Migrated VMs show as "Missing" and fail to reconcile after cross-vCenter vMotion in multi-tenant Aria Automation environments

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In Aria Automation environments utilizing multi-tenancy, virtual machine (VM) reconciliation fails after migrating (vMotion) VMs between vCenters.

When attempting to reconcile VMs migrated to a VMware Cloud Foundation (VCF) target cloud account, you may observe the following symptoms:

• VM Status: Migrated VMs enter a "Missing" state in Aria Automation and continue to be incorrectly displayed on the source cloud account.

• Missing Events: There are no reconciliation events triggered in Aria Automation. The last logged event on the deployment is typically the initial "Deployment Completed" event from the source.

• Missing Custom Properties: The custom properties of the VM deployment do not contain migrationMessage or migrationStatus.

• Data Collection: Despite the reconciliation failure, vCenter data collection remains healthy. The VM resource correctly shows up on the VCF target account/region on the backend.

• Database Output: Running a check against the execution_token table (select * from execution_token where key like '/resources/endpoints/%';) returns no output, indicating no cloud accounts are present in the table.

Environment

Aria Automation 8.18.1

VMware Cloud Foundation 5.2.2

Cause

This issue is triggered by the introduction of multi-tenancy configurations within the Aria Automation instance, which prevents the system from properly updating VM resources following a cross-vCenter vMotion. Execution token records are not generated for the managed vSphere cloud accounts.

Resolution

A permanent fix for this issue is scheduled for inclusion in Aria Automation 8.18.1 Patch 6.