Known issues

Known issues identified in Cloudera Migration Assistant 4.0.0

CMA-4369: Ozone files missing after rescan

4.0.0

After the final scan of a migration execution, migrated files may not appear in the scan results. Folders are visible, but files are not.

Rescan Ozone on the target cluster.

AMCM-4108: Example feature flag not removed from production build

4.0.0

The example-feature-flag toggle remains visible in Settings > Feature Flags in production builds.

Do not enable example-feature-flag in production deployments.

AMCM-4109: Ozone Layout Structure templates are placeholder or demo only

4.0.0

Built-in Ozone layout structure templates in the Storage Editor are placeholders and are not intended for production use.

Do not use the built-in Ozone Layout Structure templates in production. Create custom YAML layouts manually instead.

CMA-4343: Ozone Layout Provisioning (Technical Preview) limitations

4.0.0

• CMA does not validate layout definitions for volumes, buckets, or quotas.

• CMA does not verify whether the specified settings are feasible on the target cluster.

• Ozone Layout Provisioning has not been tested as part of the end-to-end migration workflow.

Use this feature for evaluation purposes only. Verify layout definitions manually before deploying. Do not rely on this feature in production migration workflows.

AMCM-4120: Feature Flags: 500 error banner not cleared after successful configuration update

4.0.0

On Settings > Feature Flags, a 500 Internal Server Error banner can remain visible after a later configuration update succeeds.

None

AMCM-4121: Feature Flags: viewer role can toggle flags; 403 does not revert toggle state; scope filter not working

4.0.0

Users with the viewer role can interact with feature-flag toggles. Failed updates can leave toggles in the wrong state, and the scope filter does not work as expected.

Restrict access to the Feature Flags page to admin users only. Do not rely on the UI to enforce viewer-role permissions.

AMCM-4123: Agent /api/agent/config endpoint is unauthenticated; agent /api/** uses HTTP Basic auth

4.0.0

The Cloudera Migration Assistant Agent exposes GET /api/agent/config without authentication, returning bootstrap details such as the auth server URI and gRPC endpoint. Other /api/** endpoints use HTTP Basic authentication.

Restrict network access to the Cloudera Migration Assistant Agent API. Enforce the TLS (ssl) profile on non-isolated deployments. Treat /api/agent/config as bootstrap-only infrastructure.

AMCM-4126: Agent UI Settings and Admin menu items do not work

4.0.0

On the Cloudera Migration Assistant Agent web UI, Settings and Admin menu items fail, show a blank page, or have no effect.

None

AMCM-4128: Plan page View Documentation link does not work

4.0.0

The View Documentation control on the Plan page fails, shows an error, or navigates to a blank page.

None

AMCM-4130: Plan page Execution tab plan filter shows invalid data

4.0.0

On the Plan page Execution tab, the plan filter dropdown shows invalid or unexpected values that do not match available plans.

None

AMCM-4134: Ozone browser navigates to parent when switching from Review tab back to Data tab

4.0.0

When the Ozone browser is navigated to a specific path on the Data tab, switching to Review and back returns the browser to the parent path instead of the previous location.

After you switch back to the Data tab, re-navigate to the Ozone path you need.

AMCM-4135: Collections item count includes parent folders, not just mapped items

4.0.0

The Collections view item count includes parent folders in the hierarchy, not only explicitly mapped items, which can inflate counts.

None

AMCM-4139: Typos present in Settings > Cloudera Replication Manager App Access Settings tab

4.0.0

The Settings > Cloudera Replication Manager App Access Settings tab contains typographical errors in user-facing text.

None. The typos appear in user-facing labels only and do not affect functionality.

AMCM-4144: HDFS scan does not support running under a custom user

4.0.0

There is no supported way to configure the Cloudera Migration Assistant Agent to run an HDFS scan as a specific Unix user. You can set CMA_MIGRATE_WITH_USER_OF_SERVICE to use a Cloudera Manager service identity (process user or Kerberos principal), but not an arbitrary username. Scans run as the agent service account by default and may miss directories owned by other users.

Ensure the Cloudera Migration Assistant Agent service account has read permissions on all HDFS directories you want to scan. Scans run as the agent service account and may miss directories owned by other users.

AMCM-4145: HDFS discovery Info column is too wide

4.0.0

On the HDFS scan Discovery tab, the Info column is wider than needed for its two action buttons.

None. The column width does not affect HDFS discovery results or scan behavior.

AMCM-4146: Selected columns are not preserved across HDFS scan result navigation

4.0.0

Custom column selections on the HDFS scan Discovery tab reset to defaults when you navigate to another directory.

Re-select your custom columns after you navigate to a new directory or page.

AMCM-4148: Assign button has no tooltip

4.0.0

On the Plan Collections tab, the Assign button lacks a tooltip while adjacent Info and Scan buttons show tooltips.

None. The Assign button works as expected; only the tooltip is missing.

AMCM-4149: Plan Collections tab does not visually separate bulk actions from selection-independent actions

4.0.0

On the Plan Collections tab, bulk actions such as Assign are not visually distinguished from always-available actions such as Info and Scan.

Select items before you click Assign. The layout does not affect how the buttons work.

AMCM-4150: Metadata tab shown for plans that have no Hive entries in collections

4.0.0

The Metadata tab appears on migration plans that contain only HDFS paths and no Hive databases or tables, which can be confusing.

You can ignore the Metadata tab on HDFS-only plans. It does not contain Hive metadata for those plans.

AMCM-4164: HDFS scan silently skips the HBase directory; not documented

4.0.0

HDFS scans skip the /hbase directory without surfacing a warning in the UI or documentation.

Account for the skipped /hbase path when planning HDFS discovery and migration scope.

AMCM-4176: Permission-denied failures in HDFS-to-Ozone migration show no actionable error message

4.0.0

HDFS-to-Ozone migrations that fail because of filesystem permission errors (for example source files owned by root:root with mode 600) do not show a clear, actionable error in the UI.

Check source file permissions before migration. Adjust permissions or ACLs on files owned by root:root with mode 600 so the replication user can access them.

AMCM-4185: CSD AutoTLS integration does not auto-enable TLS on secured clusters

4.0.0

On Kerberized clusters with AutoTLS enabled, deploying Cloudera Migration Assistant through a parcel may not enable TLS automatically. You may need to set ssl_enabled and keystore properties manually in Cloudera Manager. The Gateway default HTTP port 8090 can conflict with YARN ResourceManager.

In Cloudera Manager, set ssl_enabled to true and configure keystore location and password for each role. If the Gateway fails with port 8090 in use, change cma_gateway_server_http_port (for example to 8092).

AMCM-4212: Progress bar in code editor is misaligned and partially outside the editor area

4.0.0

When editing large Airflow DAG files in the code editor, the progress bar is misaligned and can render outside the editor with inconsistent styling.

None

AMCM-4213: Plan creation is allowed before source and target clusters have been scanned

4.0.0

Cloudera Migration Assistant allows creating a migration plan before source and target cluster scans finish, which can lead to incomplete plan data.

Wait until cluster scans complete before creating a migration plan.

AMCM-4214: Cloudera Data Engineering: mapped GitHubFile entries remain visible in UI after plan deletion

4.0.0

After deleting a Cloudera Data Engineering migration plan, mapped GitHubFile entries can remain in the database and UI with mappingStatus=MAPPED.

None

AMCM-4215: Storage Editor shows incorrect DS Quota value in table view after YAML import

4.0.0

After importing a YAML layout in the Storage Editor, the table view can show an incorrect DS Quota value while the edit drawer shows the correct value.

Open the edit drawer for a volume or bucket to verify the DS Quota value. The table view can show an incorrect number after YAML import.

AMCM-4216: Storage Editor skips folders on YAML import — only last bucket gets root folders

4.0.0

YAML import in the Storage Editor may import root folders and subfolders for only the last bucket in the file, skipping folders for other buckets.

Import YAML files one bucket at a time, or manually add folders for every bucket except the last one after import.

AMCM-4218: Storage Editor Import shows "[object Object]" instead of a readable validation error

4.0.0

When YAML import validation fails (for example a type mismatch), the Import Structure dialog shows [object Object] instead of a readable error message.

None

AMCM-4225: Replication policy submission fails if source cluster was renamed

4.0.0

Cloudera Replication Manager policy submission can fail with HTTP 500 when the source cluster was renamed after registration.

Do not rename source clusters in Cloudera Manager after you register them in Cloudera Migration Assistant. If a cluster was renamed, re-register it with its current name.

AMCM-4226: Cloudera Data Engineering Airflow Scan/Plan/Migration has schema inconsistencies

4.0.0

The data model for Cloudera Data Engineering Airflow scan, plan, and migration workflows has schema inconsistencies that can affect mapping and execution behavior.

None

AMCM-4227: Cloudera Data Engineering execution includes all plan mappings instead of only selected collection

4.0.0

When you run a Cloudera Data Engineering-to-Git execution and select one collection, the execution can include all mapped DAGs from the plan instead of only the selected collection.

Keep all mapped DAGs in a single collection if you intend to run a selective execution. Executions can include mappings from other collections.

AMCM-4230: Dead URL after session expiry

4.0.0

After session expiry, the login page can redirect to a URL that does not reopen the Cloudera Migration Assistant Master UI, leaving a blank page until you navigate manually.

After re-authenticating, open the correct Cloudera Migration Assistant Master UI URL directly in the browser.