From the console

1. After clicking Create in the cluster creation form, return to the migration wizard. Go to Migration hub > Clusters > Eligible clusters, or go to Containers > Clusters, and open the wizard for your Classic cluster.
2. In the migration wizard, navigate to the Create step in the left navigation panel.
3. Monitor the sub-operation status indicators for Policy migration, Add-on migration, and Global resources migration. Each sub-operation shows its current status.
4. When all sub-operations show a checkmark, the Create step is complete. Navigate to the Migrate step to proceed with workload migration.

If any sub-operation shows an error, expand it for details and see Troubleshoot a failed sub-operation.

From the CLI

1. Run the following command every 60 seconds until all sub-operations report completed. If any report failed, see Troubleshoot a failed sub-operation.

   ibmcloud oc replatform cluster get --cluster-id CLASSIC_CLUSTER_ID
   

   Example output (all completed):

   Sub-operation                  Status       Message
   policy-migration               completed    Policy migration complete.
   addon-migration                completed    Add-on migration complete.
   global-resources-migration     completed    Global resources migration complete.
   

   Each sub-operation reports one of the following statuses: pending, in_progress, completed, or failed. Do not proceed to the Migrate step until all report completed.

From the API

1. Poll the clusterMigrationStatus query every 60 seconds until all status fields return completed. If any return failed, see Troubleshoot a failed sub-operation.

   query MigrationStatus($id: ID!) {
     node(id: $id) {
       ... on KubernetesCluster {
         vpcMigration {
           clusterMigrationStatus {
             policyMigrationStatus          { status message errorMessage }
             addonMigrationStatus           { status message errorMessage }
             globalResourcesMigrationStatus {
               status message errorMessage
               additionalDetails { key value }
             }
           }
         }
       }
     }
   }
   

   { "id": "CLASSIC_CLUSTER_ID" }
   

   Example response (all completed):

   {
     "data": {
       "node": {
         "vpcMigration": {
           "clusterMigrationStatus": {
             "policyMigrationStatus":          { "status": "completed", "message": "Policy migration complete.",          "errorMessage": null },
             "addonMigrationStatus":           { "status": "completed", "message": "Add-on migration complete.",          "errorMessage": null },
             "globalResourcesMigrationStatus": { "status": "completed", "message": "Global resources migration complete.", "errorMessage": null, "additionalDetails": [] }
           }
         }
       }
     }
   }
   

   Each sub-operation reports a status of pending, in_progress, completed, or failed. Do not proceed to the Migrate step until all return completed.

From the console

1. On the VPC cluster overview page, click the Add-on status tile if it shows an error.
2. Review the error details displayed. Resolve the issue indicated.
3. Reopen the migration wizard. Go to Migration hub > Clusters > Eligible clusters, or go to Containers > Clusters, and open the wizard for your Classic cluster.
4. On the Create step, the failed sub-operation is highlighted. Click Retry next to the failed sub-operation to re-trigger it.
5. Monitor the status until the sub-operation shows as complete before proceeding.

From the CLI

1. Check which sub-operation failed and review the error message.

   ibmcloud oc replatform cluster get --cluster-id CLASSIC_CLUSTER_ID
   

   Example output showing a failure:

   Sub-operation                  Status       Message
   policy-migration               failed      
   addon-migration                completed    Add-on migration complete.
   global-resources-migration     completed    Global resources migration complete.
   

2. Resolve the issue, then re-trigger the failed sub-operation using the API or console — CLI retry is not available in this release. See From the API below.

3. Run the status command again every 60 seconds until all sub-operations report completed.

   ibmcloud oc replatform cluster get --cluster-id CLASSIC_CLUSTER_ID
   

   Example output (all completed):

   Sub-operation                  Status       Message
   policy-migration               completed    Policy migration complete.
   addon-migration                completed    Add-on migration complete.
   global-resources-migration     completed    Global resources migration complete.
   

From the API

1. Query the migration status to identify which sub-operation failed and read its errorMessage.

   query MigrationStatus($id: ID!) {
     node(id: $id) {
       ... on KubernetesCluster {
         vpcMigration {
           clusterMigrationStatus {
             policyMigrationStatus          { status message errorMessage }
             addonMigrationStatus           { status message errorMessage }
             globalResourcesMigrationStatus { status message errorMessage additionalDetails { key value } }
           }
         }
       }
     }
   }
   

   { "id": "CLASSIC_CLUSTER_ID" }
   

2. Resolve the issue, then call the retryMigrationSubOperation mutation to re-trigger the failed sub-operation. Replace OPERATION_NAME with one of: policy-migration, addon-migration, or global-resources-migration.

   mutation RetrySubOp($input: RetryMigrationSubOperationInput!) {
     retryMigrationSubOperation(input: $input) {
       message status
     }
   }
   

   {
     "input": {
       "clusterID":     "CLASSIC_CLUSTER_ID",
       "operationName": "OPERATION_NAME"
     }
   }
   

   Example response:

   {
     "data": {
       "retryMigrationSubOperation": {
         "message": "Sub-operation 'policy-migration' re-triggered successfully.",
         "status": "in_progress"
       }
     }
   }
   

3. Poll clusterMigrationStatus again every 60 seconds until all sub-operations return completed.

Your Classic cluster is not affected by a failed sub-operation and continues to serve traffic. If retrying a sub-operation does not resolve the issue, open a support case. Include the errorMessage value from the clusterMigrationStatus query and your Classic cluster ID so that IBM Support can investigate.