Troubleshooting CDSW to CML migration

Failed Migration

Problem: In the event your migration fails, the Migration failed indicator appears.

Solution: In Workspaces, click Options , and select Retry CDSW Migration:

CDSW to CML migration frozen with large Projects

Problem: If the Project being migrated from CDSW to Cloudera Machine Learning is large, it can get stuck, frozen, while waiting for all pieces of Project information to get migrated. After a while, the logs display that the migration was sucessful, however the UI is still unavailable:

Solution: Instruct Cloudera Data Platform manually that the migration has finished:

1. Find the Customer Resource Number (CRN) of the new workspace from the Control Plane.
2. Open a shell into the cdp-embedded-db-0 pod which is in the cdp namespace. This can be done from the Kubernetes dashboard or with kubectl.
3. Add a new entry into the database that tells the system that the migration is completed:

   psql
   \c db-mlx
   INSERT INTO event(instance_id, resource_type, status, operation, user_id) SELECT id, 'mlx_instance', 'started', 'validateMigration', creatorcrn from mlx_instance where mlx_instance.crn=‘##<crn>###';

Following these steps, the Cloudera Data Platform UI is updated, and displays the information that the migration must be validated. You can continue the migration process.

Viewing logs

Problem: In the event your migration fails, and the retry also fails, you need to get information about the failure.

Solution: In Workspaces, click Options , and select View Event Logs.

Problem when migrating parcels to a new CML workspace

If parcels are located in a custom directory specified by parcel_repo_home in Cloudera Manager, instead of the default location (/opt/cloudera/parcels), then the CDSW to CML migration script will not find them.