Version 5.0

Troubleshooting

Learn about troubleshooting steps that you might find helpful if you run into problems using Migrate for Compute Engine.

Error: Required compute.subnetworks.use permission

A Shared VPC allows an organization to connect resources from multiple projects to a common Virtual Private Cloud (VPC) network, so that they can communicate with each other securely and efficiently using internal IPs from that network.

Migrate for Compute Engine lets you deploy a Compute Engine instance to a project that has access to a Shared VPC. However, if you have not assigned the compute.subnetworks.use role to the Migrate for Compute Engine default service account, you see an error message in the form below when you try to deploy the Compute Engine instance:

"Create instance of VM "my-vm" from source "my-proj" to target project "target-proj" using Compute Engine instance name "instance-id" failed due to: Required 'compute.subnetworks.use' permission for 'projects/vpc-proj/regions/us-central1/subnetworks/shared-central1'

Ensure that you assign the compute.subnetworks.use role on the Shared VPC host project to the Migrate for Compute Engine default service account as described in Configuring permissions for a Shared VPC.

Error: The user does not have access to service account

As part of Configuring the target for a migrated VM, Migrate for Compute Engine lets you assign a service account to a Compute Engine instance running on a target project.

However, to be able to assign a service account to a Compute Engine instance running on a target project, the default Migrate for Compute Engine service account on the host project must have the Service Account User role on the target service account.

If you assign a service account to a Compute Engine instance, but the host project does not have the Service Account User role on the target service account, then you see the following error when you try to test-clone or cut-over the VM:

Test-Clone of VM "my-vm" from source "source-vm" to target project "target-proj" using Compute Engine instance name "my-instance" failed due to: The user does not have access to service account 'target-service-account-email'. User: 'host-user-account-email'. Ask a project owner to grant you the iam.serviceAccountUser role on the service account

Ensure that the default Migrate for Compute Engine service account is configured correctly to allow access to the target service account. See Configuring permissions on target project service account for more.

Error: Report generation failed due to vCenter maximum query limit exceeded

To help you determine the optimal settings for the Compute Engine target, Migrate for Compute Engine lets you create a source VM utilization report. This report displays information about resource allocation and utilization for the source VMs deployed on vCenter.

The report is generated from data collected on vCenter. When generating the report, you might see an error in the form below indicating that a vCenter quota limit has been reached:

Report generation for source source connected to vCenter vcenter failed due to vCenter maximum query limit exceeded. Details: VC message

See this vSphere article for more information on increasing the quota limit.