VMs migrated by cross-vCenter vMotion not reconciling in Aria Automation: duplicate VMs remain on each cloud account

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• After vMotion of a VM from one vCenter to another, we see 2 VMs in the inventory of the Aria Automation: one in the discovered and one under managed.
  • One VM is showing from the old vCenter and the discovered VM is showing as being on the destination vCenter.
  • While the vMotion operation completes successfully and the VM remains powered on and functional, Aria Automation is not recognizing these two VMs as representing the same managed object
• The vCenters are not together in Enhanced Linked Mode (ELM), but the source vCenter is in ELM with another vC server.
• The Requirements from the article Virtual Machine reconciliation after vMotion migration have been met.
  • Both source and destination vCenters are managed by the same Aria Automation instance (Cloud Accounts created).

Environment

• VMware Aria Automation 8.18.1, including with patches 1 to 3

Cause

• There is an issue which can affect VMs when migrating from a vCenter in ELM, to one which is not.

Resolution

Engineering are aware of this issue and a fix will be provided in Aria Automation 8.18.1-patch4

For more information, please contact Broadcom Support referencing this article.