In VCF Operations, users may observe that the Summary page for a vCenter instance managed via the VMware Cloud Foundation (VCF) Management Pack displays incorrect metadata.
The URL for a specific vCenter (e.g., vCenter1.example.com) incorrectly shows the URL of a different vCenter (e.g., vCenter2.example.com). (Refer the Screenshot below)
This behavior persists even after performing a Sync Inventory task from the Inventory > VCF Instances > [Affected vCenter Name] > Actions menu.
Standalone vCenter adapter instances in the Administration > Integrations page may appear hung or stay in a perpetual "loading" state when attempting to edit.
Taking the VCF Operations cluster offline and online does not resolve the metadata mismatch.
VCF Operations 9.x
This is a cosmetic defect in the inventory retrieval logic. When a shared NSX instance is present, the backend sees multiple vCenters as potential "children" of the infrastructure. The UI logic incorrectly selects the first available vCenter object from the list to display the FQDN, rather than mapping the specific vCenter assigned to that Domain.
This issue is resolved in VCF Operations 9.1. The VCF Operations 9.1 release is tentatively scheduled for April 2026.
Because this is a display-only issue with no impact on data collection or system stability, manual workarounds are not recommended. Customers should plan to upgrade to version 9.1 to resolve the metadata mapping logic.