VM Instance UUID mismatch in Aria Automation after HCX RAV migration.
search cancel

VM Instance UUID mismatch in Aria Automation after HCX RAV migration.

book

Article ID: 445983

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  1. Day 2 actions for affected deployments are grayed out and unavailable (except for "Delete" and "Unregister").
  2. VM deployments shows status as "Missing" or "Unknown."
  3. Backup jobs (e.g., Dell Networker, Veeam) for migrated VMs fail or trigger a new full backup.
  4. The issue is observed after performing HCX Replication Assisted vMotion (RAV) migrations of virtual machines between clusters within the same vCenter Server environment.

 

 

Environment

  • VMware Aria Automation 8.18.x
  • VMware HCX 4.11.x

Cause

  1. Mismatch in the VM Instance UUID (vc.uuid) introduced during an HCX RAV migration within a single vCenter. vCenter Server requires every VM in its database to have a unique vc.uuid.
  2. During the migration cutover, both the source and target VM temporarily coexist.
  3. To prevent a collision, vCenter automatically assigns a new instanceUuid to the target VM. Aria Automation loses its association because it relies on the original UUID.

Resolution

  1. This fix is scheduled to be included and delivered in one of the upcoming release. Refer to this article to download latest HCX version Download Broadcom products, patches and software
  2. To review, analyze & resolve this issue, contact Broadcom Support and open a support case referencing this KB 445983.

Additional Information

Note: For defects and enhancements, subscribe to the article to be updated on fix status. Subscribe to a Broadcom knowledge article by article or product