Why is my Classic-to-VPC migration stuck in global resource migration?

Classic infrastructure

Your Classic-to-VPC cluster migration does not complete the global resource migration sub-operation.

During global resource migration, the migration service also migrates Ingress controllers for Red Hat OpenShift on IBM Cloud clusters. In the migration wizard (navigate to the navigation menu > Migration > Get started > Clusters > Eligible clusters and click Open wizard next to the source cluster), on the Phase 1 Create step (Create VPC cluster page), the migration job does not progress. In the VPC cluster card, the Global resources migration field remains stuck with statuses such as Creating ingress subdomains, Enabling ingress ALBs, or Enabling ingress controllers.

The account reached its VPC load balancer quota in the target region where the VPC cluster is being provisioned. The migration cannot create the VPC load balancers that the Ingress components require.

To resolve the issue, request a VPC load balancer quota increase for your account and region.

  1. Review the VPC load balancer quota for your account and region. For more information, see Quotas and service limits.

  2. Open a support case to request a VPC load balancer quota increase for the region.

    1. Go to the IBM Cloud Support Center.
    2. Click Create a case.
    3. Select VPC Infrastructure as the offering.
    4. In the case description, specify your account, the target region where the VPC cluster is provisioned, your current VPC load balancer quota, and the requested quota increase.
  3. After the quota increase is applied, the stuck migration job resumes automatically. You can monitor the migration progress to verify that the global resource migration completes. For more information, see Monitor global resource migration.