Error: "Identity broker instance not available" or SSO login failure - VMware Cloud Foundation 9.1

Products

• VCF Operations

Issue/Introduction

Single Sign-On (SSO) login fails and Identity Broker (vIDB) configuration errors occur following an upgrade to VMware Cloud Foundation (VCF) 9.1 in VCF Operations. Note that executing the delete_vidb.py script from KB 444724 may fail with "Identity Broker was not found" if an incorrect FQDN (such as a lab system FQDN) is used instead of the failing system's FQDN.

Symptoms:

• SSO login fails after upgrade.
• "An identity broker instance is not available for configuring Single Sign-On" error in VCF Operations UI.
• delete_vidb.py script fails with "Identity Broker was not found" or similar.
• java.lang.IllegalArgumentException: Unable to fetch the metric values for VCF Domain in vcops-bridge.log.

Environment

• VMware Cloud Foundation (VCF) 9.1
• VCF Operations (formerly Aria Operations)

Cause

VCF Operations references a stale UUID for the Identity Broker (vIDB) appliance following a failed Lifecycle Management (LCM) orchestration or reinstallation. Running delete_vidb.py from KB 444724 fails when an incorrect lab system FQDN is provided instead of the failing system's FQDN.

Resolution

When running delete_vidb.py (KB 444724), verify that the correct FQDN of the failing system is passed rather than a lab system FQDN.

Additional Information

KB 444724:  Deletion of Identity Broker from VCF Operations 9.1