"No compatible VCF Instance" error while trying to configure SSO after VCF 9.1 upgrade

Products

• VCF Operations

Issue/Introduction

• When logging into the VCF Operations UI, there is no SSO log in option - only a local one.
• In VCF Operations UI under Fleet Management > Identity & Access > VCF SSO Overview > Configure VCF SSO > Choose Deployment Mode indicates SSO is not configured.
• Error Message: "An identity broker instance is not available for configuring Single Sign-On."

Environment

• VCF Operations 9.1.0

Cause

During the upgrade from 9.0.2 to 9.1.0, when the LCM orchestration fails and the VIDB appliance is reinstalled, a new resource UUID is assigned. Here VCF Operations continues to reference the stale UUID of the old appliance, leading to a "no compatible Identity Broker" error.

Resolution

1. Perform a cleanup of VIDB using the cleanup tool. For detailed steps, see Scripted components cleanup from VCF Operations.
2. Install the Identity Broker from the VCF Operations UI:
   1. Log in to the VCF Operations Console as an Administrator
   2. Navigate to Fleet Management > Lifecycle > VCF Management.Go to Components and click Add Component > identity broker
   3. Select New Install and follow the wizard to input your Deployment, Certificate, and Infrastructure details.
   4. Provide a minimum of 4 Cluster Node IP Addresses for the vIDB appliances and complete the network setup
   5. Submit the request to complete the installation and registration.
3. After successful installation and registration, wait approximately 10-15 minutes for the VCF Operations polling cycle to complete.
4. The SSO configuration option becomes available in the UI. 

Additional Information

Broadcom Contact Support.