VM shows as discovered after cross-vCenter vMotion in Aria Automation 8.18.1

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Aria Automation 8.18.1 Patch 3, you may observe that a virtual machine (VM) does not correctly update its vCenter association following a cross-vCenter vMotion. Although both the source and destination vCenters are added to Aria Automation, the VM remains linked to the old deployment while simultaneously appearing as a "Discovered VM" under the new vCenter.

Environment

 

• Product: VMware Aria Automation

• Version: 8.18.1 Patch 3

 

Cause

This issue is caused by a bug in the Aria Automation database where the Managed Object Reference (MoRef) ID for the VM is not correctly updated during the cross-vCenter migration process. This is tracked internally with a PR filed on it.

Resolution

The fix for this issue is tentatively planned for Aria Automation 8.18.1 Patch 4 and will also be included in VCF 9

Additional Information

For VCF  and Aria Automation customers, please note that no specific release dates can be provided for future patches.