Infrastructure migration fails to create a Cloud Zone with "Unable to find a compute resource" errors

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Symptoms:

• Infrastructure migration fails to create a Cloud Zone with an error similar to:

Unable to find compute resource name, possibly due to a problem with endpoint data enumeration.  Please re-run migration.

Environment

VMware vRealize Automation 8.2.x

Cause

The error occurs because the name of the Data Center or Cluster was manually changed within VMware vCenter outside of vRealize Automation (vRA).  This causes an inconsistency in the vRA database that migration is unable to recover from.  As migration does not communicate directly with vCenter, only the source vRA, there is no way to pre-check the reservation-to-cluster connection.  The condition of the vRealize Automation 7.x source system should be verified prior to attempting an Assessment and Migration.

Resolution

This issue is resolved in vRA 8.3 GA and above.

Workaround:
The migration report is correctly detailing the issue that prevented the migration from succeeding.  Both assessment and migration communicate only with the vRealize Automation 7.x source system.  The error is generated after a vCenter instance was added to vRealize Automation 8.x as a cloud account and the cluster referenced by the vRealize Automation 7.x reservation is added as a cloud zone.  During this process, the cluster is found to be unavailable.

There are a few possible workarounds:

1. Revert the name of the vCenter Cluster to match what the vRealize Automation 7.x Reservation is configured for, then re-run the migration.
2. Create a new reservation in vRA 7.x that duplicates the existing failing reservation. Be sure to select all the same storage and other settings as the failing reservation. Then, move all of the VMs (one-by-one) from the failing reservation to the new reservation. Re-run the migration.
3. Engage GSS and reference Problem Report #2713699, update #7.
4. If none of the above solutions are acceptable, the reservation may be disabled in vRA 7.x. This will allow the migration to continue for other reservations in the business group. However, the Cloud Zone in vRA 8 must be manually created and any VMs in that reservation can only be on-boarded, not migrated. Before choosing this path, it must be understood that on-boarding is a very different operation than migration. It communicates only with vSphere, not the vRA 7.x source system, so constructs specific to vRA, such as network profiles and vRealize Orchestrator (vRO) workflows, will not be carried over.

Additional Information

Create a vCenter cloud account in vRealize Automation
What’s New with vRealize Automation 8.3 – Technical Overview