Onboarded VMs not reflected in Project or Cloud Zone usage metrics in Aria Automation 8.18.1
search cancel

Onboarded VMs not reflected in Project or Cloud Zone usage metrics in Aria Automation 8.18.1

book

Article ID: 405089

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Aria Automation 8.18.1, onboarded vSphere virtual machines may not appear in project or Cloud Zone usage metrics, even though they are visible in the Deployments and Virtual Machines views. This impacts quota enforcement and reporting.

  • Onboarded VMs are visible in the UI but not counted against project or Cloud Zone quotas.

  • API calls to /iaas/api/projects/<project-id> return zero instances or memory usage.

  • VMs were onboarded successfully but later vMotioned to other hosts through normal DRS activity for balancing resources across hosts.

  • Usage metrics no longer reflect actual deployed resources.

    • You may see a negative integer value for the consumption of resources when polling for resource consumption statistics through the API.

Environment

VMware Aria Automation 8.18.1 GA through Patch 3.

Cause

This issue occurs because the migration reconciliation logic released in 8.18.1 depends on the presence of the project custom property to track group resource placement. Onboarded VMs do not have this property by default.

When a vMotion occurs, reconciliation cannot verify ownership and incorrectly removes the placement association, even if the VM has not changed Cloud Zones.

Resolution

Resolution

This issue is resolved in Patch 4 for Aria Automation 8.18.1, which updates the reconciliation logic to reliably track onboarded VM ownership. Customers are strongly advised to wait for Patch 4 rather than apply manual fixes.

Workaround

While temporary workarounds exist, they are not recommended due to scale, operational complexity, and potential for error:

  • Option 1: Disable migration reconciliation using the enable.vm.migration toggle (not advised in dynamic or production environments).

  • Option 2: Manually patch onboarded VMs by adding the project custom property through extensibility workflows or scripts (not scalable for large environments).