Upgrade failure scenarios for Identity Broker in VCF 9.0.x to 9.1

Products

• VMware Cloud Foundation

Issue/Introduction

This article serves as a central reference guide for identifying and resolving known failure scenarios encountered when upgrading the VCF Identity Broker (VIDB) from from version 9.0.x to 9.1. It consolidates symptoms, environmental requirements, and links to specific resolution paths for common upgrade disruptions, including network misconfigurations, discovery failures, and metadata discrepancies.

Environment

• VMware Cloud Foundation (VCF) 9.1
• VMware Identity Broker (vIDB)

Resolution

The upgrade can be continued by skipping Identity Broker; however, the component will remain on version 9.0.x and 9.1 features are unavailable. To resolve specific failure scenarios, refer to the following links:

1. Network Discrepancies:
   1. Upgrade fails with error "Errors occurred during running prechecks. We strongly recommend re-running prechecks before starting the upgrade." if the VCF Identity Broker is deployed in a different network than the VCF Management Service runtime network, follow the manual steps in: Redeploy VCF Identity Broker 9.0.x to a Supported Network and Datastore for Upgrade to 9.1.
      
      
2. Discovery Failures:
   1. If Identity Broker is not discovered during the Fleet LCM “Import VCF Operations” step with error: “Failed to discover component of type 'VIDB'.”, Follow the steps from KB "Deploy VCF Management Components" task fails during "Import VCF Operations in Fleet Lifecycle" subtask.
      
      
3. Registration Cleanup:
   1. If the Identity Broker is re-deployed and it fails with error: “Power Off Source Cluster. Status: Failed. Step vmsp_upgrade_vidb failed.”, follow the steps from KB: Deletion of Identity Broker from VCF Operations 9.1 to clean up previous records.
      
      
4. Label/Instance Errors:
   1. If multiple VCF instances were configured in 9.0, the installation label must be updated. Follow the steps from KB: Error: "Internal error occurred" while upgrading Identity Broker from 9.0.2 to 9.1, although the upgrade is successful.
      
      
5. Inventory Path Discrepancy: 
   1. If the upgrade fails at the "Power Off Source Cluster" step due to manual relocation of VMs in vCenter, Follow the steps from KB: VIDB Upgrade to 9.1 fails at Power Off Source Cluster step with Error vmsp_upgrade_vidb failed.