VM Status "Missing" After Cross-vCenter vMotion in Multi-Tenant Aria Automation
search cancel

VM Status "Missing" After Cross-vCenter vMotion in Multi-Tenant Aria Automation

book

Article ID: 416225

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After performing a cross-vCenter vMotion, a Virtual Machine (VM) no longer appears correctly within the Aria Automation deployment view.

  • The VM may be missing or show an incorrect status.

  • When inspecting Deployment > Machine > Custom Properties, the migrationStatus property is stuck at STARTED.

  • This issue specifically impacts Multi-Tenant Aria Automation environments.

Environment

Aria Automation 8.18.x

Cause

It's a known problem for multi-tenant configuration. Engineering is aware about the issue.

Resolution

There is currently no permanent fix available for version 8.18.x. Engineering is actively developing a resolution, which is planned in an upcoming Aria Automation patch.

Workaround

If you encounter this state, you must manually re-sync the resource:

  1. Unregister the affected VM from the existing Aria Automation deployment.

  2. Onboard the machine into a new deployment to restore management capabilities.

Note: Please Subscribe to this article to receive automated notifications once the official patch is released.

Powered by Wolken Software