Aria Operations reports stale or duplicate vApp references for VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• Aria Operations API or inventory tree lists significantly higher count of "Discovered" vApp entries (e.g., naming convention "Discovered testvcloud-####") for a particular OrgVDC in VMware Cloud Director.
  
  
  
  
• VCD (VMware Cloud Director) GUI shows correct object counts, but API calls report stale records.
• The VCD database contains over 1,000 stale entries in the vm_container table.
• These VMs were created under the OrgVDC resource pool in vCenter as part of a migration test performed by a migration/DR tool(e.g., HCX) and later cleaned up. VCD imports these VMs when VM discovery is enabled. 

Environment

Aria Operations 8.x
VMware Cloud Director 10.x

Cause

 The issue is caused by stale vApp references in the VCD database. When objects are removed at the vCenter layer, VCD may retain database entries if the synchronization fails. Aria Operations continues to collect these objects because they exist in the VCD database

Resolution

This issue requires manual database modifications. To resolve this issue, please open a Support Request with Broadcom Technical Support and note this Article ID (450704) in the problem description. For more information, see Creating and managing Broadcom support cases. 

Warning: Take a snapshot (non-memory and non-quiesced) of all VCD cells and back up the database before proceeding. For backup steps, see Backup and Restore of Your VMware Cloud Director Appliance .

Additional Information

VMs that are imported as part of VM discovery, will be listed with "Discovered-VMname" naming convention in VCD database. For more information about VM discovery feature, see VM discovery in VMware Cloud Director. 

 To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.