VCF Operations UI Displays Configure SSO Disabled with NullPointerException in vcfops-bridge Logs

Products

• VCF Operations

Issue/Introduction

The "Configure SSO" option in the VCF Operations user interface remains disabled. This issue occurs when vIDB configuration synchronization fails due to inventory topology ambiguity.

• The "Configure SSO" button is greyed out.
• API query /suite-api/api/fleet-management/iam/vidbs indicates an unhealthy status (NOT_ELIGIBLE).

  "vidbStatus": { 
    "eligibilityStatus": "NOT_ELIGIBLE", 
    "reasons": ["INVALID_VIDB_VERSION", "SETUP_INPROGRESS"] 
  }, 
  "healthy": false

• Review of vcfops-bridge  logs reveals a NullPointerException when attempting to derive the VCF instance ID from the vCenter resource.

  [com.vmware.vcops.bridge.server.vidb.persistence.VidbCurrentIDPConfigService.createIDP] - Persisting IDP for vidb <vidb_id>
   ERROR vcfops-bridge  [ops@<node_id> threadId="<thread_id>" threadName="ServerConnection on port 10000 Thread <thread_num>" operationId="<operation_id>"] [com.vmware.vcops.bridge.server.vidb.api.impl.CurrentStateApi.lambda$6] - Unable to update current idp state with exception
  java.lang.NullPointerException: Cannot invoke "java.util.UUID.toString()" because the return value of "com.vmware.vcops.bridge.server.vidb.model.CurrentIDPConfiguration.getVcfInstanceId()" is null

Environment

VCF Operations 9.1

Cause

An orphaned standalone vCenter adapter resource exists alongside the official VCF adapter registration for the same Management vCenter. This duplicate registration disrupts the inventory topology hierarchy, preventing the bridge service from mapping the vCenter to its parent VCF domain.

Resolution

To resolve this issue, follow the below steps

1. Log into the VCF Operations user interface as an administrator.
2. Navigate to Administration > Integrations > Inventory Accounts.
3. Locate and delete the orphan or duplicate standalone Management vCenter adapter resource.  (ensuring the primary VCF adapter registration remains intact) as per the KB: Duplicate vCenter instances appear in VCF Operations after VCF deployment or upgrade
4. Ensure the primary VCF adapter registration remains intact.
5. Allow the vIDB configuration sync job to re-run or restart the vcfops-bridge service.
6. Verify that the API endpoint /suite-api/api/fleet-management/iam/vidbs returns a healthy status.

Additional Information

1. If the issue persists, ensure that no other duplicate accounts exist in the inventory.
2. If you need further assistance, please reach out to Contact Broadcom Support.