VIDB shows as not configured after upgrade - VCF Operations 9.1
book
Article ID: 443148
calendar_today
Updated On:
Products
VCF Operations
Issue/Introduction
- Multiple VCF instances are registered in VCF operations under Administration → Integrations → VMware Cloud Foundation
- One of the SDDC management domains is running version 9.1 while its associated vCenter is still on version 8.0.x.
- IDP is already configured in VIDB and SSO users can sign in successfully
- The UI shows Start next to Configure Identity provider when navigating to Manage → Fleet Management → VCF SSO Overview → Configure VCF SSO

Environment
- VCF Operations 9.1.x
- vCenter 8.0.x
Resolution
| Note: Only proceed with these steps if you are experiencing the symptoms described in the Issue/Introduction. |
Prerequisites:
| Requirement | Detail |
| Credentials | A suite-api username and password with sufficient privileges |
| Run as | root |
| Run on | The VCF Operations primary node |
Instructions for running the script:
- Download the update-current-state.sh attachment provided below
- Use Winscp or scp utility to copy the script to VCF Operations tmp directory:
scp update-current-state.sh root@<vrops-hostname>:/tmp/
- SSH into the vrops node as root:
ssh root@<vrops-hostname>
- Execute the script:
bash /tmp/update-current-state.sh
- The script will ask you for several details. Please enter them when prompted.
- Once completed navigate to Manage → Fleet Management → VCF SSO Overview → Confirm Identity Broker is visible
Feedback
thumb_up
Yes
thumb_down
No