VCF 9.0.2 to 9.1.0 upgrade issue with IDB, result in SSO not being available

Products

• VCF Operations

Issue/Introduction

• When logging into the VCF Operations UI, there is no SSO log in option - only a local one
• In the VCF Operations UI> Fleet Management > Identity & Access > VCF SSO Overview > Configure VCF SSO > Choose Deployment Mode page it appears that SSO is not configured, when it should be, this is what is seen -

  • Choose Deployment Mode

    • 1. Choose Deployment Mode

 

Instance // Embedded
An identity broker instance is not available for configuring Single Sign-On. If the identity broker in instance mode has not been deployed, navigate
to the Lifecycle page to initiate its deployment. In cases where the identity broker has been set up in embedded mode within the VCF Instance, either
reset the configuration or migrate from embedded mode to an instance.

• • • 2. Choose Identity Broker

No compatible VCF Instance

Environment

VCF 9.1.0.0

Cause

• During the 9.0.2 to 9.1.0 upgrade, the LCM orchestration failed during the process
• Subsequently, the external VIDB appliance was inadvertently reinstalled to try to recover
• However, the newly reinstalled VIDB appliance was assigned a new resource UUID, which was never re-registered in VCF Operations
• Consequently, VCF Operations continued to reference the stale resource entry of the old VIDB appliance.
• As the old appliance is no longer in existence, its version data was missing
• This caused VCF Operations to treat it as an ineligible authentication source and then to report no compatible Identity Broker as being available for SSO configuration, result in the behaviour observed

Resolution

Please open a case with Broadcom Technical Support to have the issue resolved.