A duplicate VMware Cloud Foundation (VCF) instance was discovered in the VCFA portal, displaying two entries for the same instance one registered by its Hostname and the other by its IP address.
By checking the workload domain mapping, it was verified that the instance registered with the IP address was the duplicate. While a cleanup had already been performed in VCF Operations, the duplicate remained visible in VCFA and required manual removal.
VCF Automation 9.x
This is the result of a known synchronization anomaly. When a duplicate VCF instance is cleaned up in VCF Operations, the deletion fails to automatically propagate to VCFA.
Broadcom is aware of this issue and plans to resolve it in an upcoming feature release.
Workaround:
NOTE: Make sure to take a full SFTP backup of VCFA refer to the following Broadcom Doc
The stale duplicate instance was manually deleted from VCFA using the API via the Swagger UI. The following steps were performed to force the removal of the specific stale record from the backend:
Extracted the URN ID of the duplicate instance from the browser address bar.
Confirmed the exact ID using the GET /1.0.0/vcfinfraEndpoints API call.
Safely removed the duplicate using the DELETE /1.0.0/vcfinfraEndpoints/{id} API call, which successfully returned a 200 response code.
Refreshed the VCFA UI to verify the duplicate instance was completely removed from the portal.