Error: Metrics Provider is fetching 2 resources when it was expected to fetch 1 in Aria Automation after HCX triggered cross vCenter migration
search cancel

Error: Metrics Provider is fetching 2 resources when it was expected to fetch 1 in Aria Automation after HCX triggered cross vCenter migration

book

Article ID: 448742

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Navigating to the Aria Automation UI > Virtual Machine shows the error: RuntimeException: Metrics Provider is fetching 2 resources when it was expected to fetch 1.
  • Managed deployments may briefly appear in an "Unknown" status.
  • Day 2 actions are unavailable for the affected VM.

  • The error is generated by the vROps connector code (PerformanceMetricsServiceImpl.java) when the metrics provider fetches the resources and the resulting list size is greater than 1.

Environment

Aria Automation 8.18.x

Cause

  • The issue is caused by duplicate compute_state records existing simultaneously in the database with the exact same instanceUuid.
  • When a virtual machine undergoes a cross vCenter migration via HCX, its underlying infrastructure identifiers such as the Managed Object Reference (MoRef) change.
  • During the next scheduled Data Collection cycle (which runs every 10 minutes), VMware Aria Automation flags the modified VM as a new asset and creates a new database record with a unique resourceId.
  • Under normal product behavior, an automatic reconciliation process marks the older, stale record as "Retired," and an internal background process purges it after approximately 24 hours.
  • However, before this 24-hour purging window completes (or if a custom "Fix Deployment" workflow is executed prematurely), both records remain active.
  • When the VMware Aria Operations connector executes a PerformanceMetricsQuery, the query returns multiple resources instead of exactly one (resources.size() == 1), triggering the exception.

Resolution

Kindly contact Broadcom Support and open a support case referencing this KB 448742.

Additional Information

Subscribe to this article to be updated on fix status (Reference: Article 275360).