Cloudera Docs

Troubleshooting Airflow DAG migration to Git [Technical Preview]

Interpret common failures, scan gaps, Git publishing failures, and authentication errors when migrating Cloudera Data Engineering Airflow DAG assets into Git-backed control planes with Cloudera Migration Assistant.

Before you begin

Each resolution builds on Setting up to Cloudera Workflow Orchestrator Git migration prerequisites when credentials or Git provider routes fail.

Symptom

Discovery is empty after scans.

Cause

Incomplete command state or restrictive collection filters masking rows.

Remedy

  1. Validate command transcripts.
  2. Temporarily clear filters to confirm that the artifacts exist.

Symptom

Virtual clusters list zero DAGs.

Cause

Knox authentication halted mid-scan (SKIPPED log entries).

Remedy

Work with administrators to reaffirm Cloudera Manager credentials powering the CMA Agent.

Symptom

Duplicate dag_id badges appear.

Cause

Separate virtual clusters authored identical identifiers.

Remedy

Rename offending DAG IDs on the Workloads tab editor in your DAG migration plan.

Symptom

Execution phase 8.1 faults occur.

Cause

Stale local artifact caches on CMA Agents.

Remedy

Rescan Cloudera platform workspaces, then regenerate executions.

Symptom

Git step fails authentication.

Cause

Expired personal access tokens or underscoped PAT scope.

Remedy

Administrators rotate CMA_AGENT_CLUSTER_GIT_TOKEN in the advanced configuration snippet and recycle CMA Agent services.

Symptom

Git rejects base branch selection.

Cause

CMA_AGENT_CLUSTER_GIT_BRANCH was deleted upstream.

Remedy

  1. Restore branch names or refresh configuration.
  2. Restart CMA Agent services once secrets synchronize.

Symptom

Pull Request links are missing after the run.

Cause

Upstream provider API errors swallowed in CMA Master diagnostics.

Remedy

Inspect Master logs with Git webhook availability from CMA Agent networks.