vCenter object cannot be expanded on the Aria Operations inventory

Products

• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

• The inventory for a vCenter instance could not be expanded in Aria Operations UI.
  
  
  
• A simple ping test from the Cloud Proxy to the Primary node resulted in 100% packet loss.
  
  

• Verified cloud proxy ,/storage/log/vcops/log/collector.log and found below entries :

  YYYY-MM-DDTHH:MM:SS,WARN  [Collector worker thread 6]  (506493) com.vmware.adapter3.diagnostics.DiagnosticsAdapter.computeFindings - rule evaluation failed, will run again in 300 seconds
  YYYY-MM-DDTHH:MM:SS,897+0000 WARN  [Collector worker thread 20]  com.integrien.alive.collector.Collector.processAutoDiscovery - Discovery result for adapter 471178 of kind VMWARE_INFRA_HEALTH is empty. Dropping empty discovery result.
  YYYY-MM-DDTHH:MM:SS,769+0000 ERROR [pool-3-thread-1]  com.vmware.vcops.collector.relay.http.HttpCommunicator.exchangeChunks - Failed to exchange chunks: status code = 504: ErrorMessage{apiErrorCode=0, httpStatusCode=504, message='Gateway Timeout', inputBodyLocation=null, validationFailures=null, moreInformation=[]} com.vmware.ops.api.model.common.ErrorMessage@94428864
  YYYY-MM-DDTHH:MM:SS,769+0000 ERROR [pool-3-thread-1]  com.integrien.alive.collector.ChunksTransferAgent.runExchange - Failed to transfer chunks. Error: Exchanged chunks result (CollectorChunksResult) is null.
  YYYY-MM-DDTHH:MM:SS,181+0000 WARN  [Collector worker thread 3]  (471179) com.integrien.alive.common.adapter3.AdapterBase.collectAdapterInstanceMetrics - No collect result found in adapter instance resource 'Configuration Management - aria-ops-BCF2-rc2', resId=471179, adapter 'ConfigAdapter'.
  YYYY-MM-DDTHH:MM:SS,182+0000 WARN  [Collector worker thread 3]  com.integrien.alive.collector.Collector.processAutoDiscovery - Discovery result for adapter 471179 of kind VCF_UNIFIED_CONFIG is empty. Dropping empty discovery result.

Environment

Aria Operations 8.18.x

 

Cause

The issue occurs due to a misconfiguration in the external Load Balancer and its associated network routing path.

Although the Aria Operations services remain healthy, communication between the Cloud Proxies and the backend services fails because traffic is either dropped or incorrectly routed in transit. This condition is typically observed as 100% packet loss and HTTP 504 Gateway Timeout errors.

The root cause is an internal routing misconfiguration on the Load Balancer, which prevents requests originating from the Cloud Proxies from being forwarded correctly to the backend Aria Operations services.

Resolution

To resolve the issue, please engage your network team and request validation of the following:

1. Perform a packet capture on both sides of the communication path between the Cloud proxies and load balancer.
2. Review the firewall rules and session timeout settings between the involved VLANs.