dsmpostgres objects are not removed from VCF Operations inventory after deletion in VCF Automation (VCFA)

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Database instances (dsmpostgres objects) deleted from VCF Automation (VCFA) continue to appear in the VCF Operations inventory.
• These objects may remain visible for several weeks after deletion.
• The objects may show a "No Data Receiving" status but remain in a "Collecting" or "Stale" state within the inventory.

Environment

VCF Operations 9.0.x

Cause

• Version Limitation: In VCF Operations 9.0.x, the auto-deletion feature for these specific object types is not yet natively supported.
• Configuration: The default retention period for non-existing objects in the application adapter is governed by the MAX_COLLECTION_CYCLE_FOR_NOT_EXISTING_STATE property, which is set to a high value (2016 cycles) by default, preventing timely cleanup.

Resolution

Native integration and automatic deletion for Data Services Manager (DSM) are introduced in later releases of VCF operations. For environments on version 9.0.x, use one of the following workarounds:

Method 1: Manual Deletion

1. Log in to the VCF Operations UI.
2. Navigate to Infrastructure Operations > Configuration > Inventory Management.
3. Search for the dsmpostgres objects that have been deleted from VCFA.
4. Select the objects and click the Delete Object (X icon) to remove them from the inventory.

Method 2: Update Adapter Configuration (Cloud Proxy)

Modify the collection cycle threshold on the Cloud Proxy to accelerate the removal of objects that no longer exist.

1. Log in to the Cloud Proxy appliance via SSH as the root user.
2. Navigate to the adapter configuration directory: cd /usr/lib/vmware-vcops/user/plugins/inbound/AppOSUCPAdapter3/conf/
3. Backup the configuration file: cp config.properties config.properties.bak
4. Edit the file: vi config.properties
5. Locate and update the following property from 2016 to 7: MAX_COLLECTION_CYCLE_FOR_NOT_EXISTING_STATE=7
6. Save the file and restart the collector service to apply the change: service vmware-vcops restart collector

Additional Information

• Later versions of VCF operations provides Native Integration for DSM, which includes automated lifecycle management and inventory synchronization for these objects.
• Reducing the collection cycle threshold to 7 ensures that objects not detected for 7 consecutive cycles are marked as "Not Existing" and removed according to global data retention policies.