Error: Platform Health Check - wrong resource state during Identity Broker upgrade

Products

• VCF Operations

Issue/Introduction

During the upgrade of VCF Identity Broker (vIDB) from 9.0 to 9.1, the upgrade pre-check may fail with a "wrong resource state" error, preventing the upgrade from proceeding. This issue is typically caused by a configuration metadata mismatch in the vIDB cluster.

Symptoms:

• The pre-check fails with the following errors:

  • Platform Health Check Error [platform-control-plane-core : # of # resources are not ok: [RESOURCE_ID]: wrong resource state: InProgress - Rolling 3 replicas with outdated spec (1 replicas up to date);] [VCFMS-HEALTH-002]

  • Platform Health Check Error [platform-package-core : # of # resources are not ok: vmsp-platform: wrong resource state: InProgress - package deployment is in progress;] [VCFMS-HEALTH-002]

  • Platform Health Check Error [platform-machines-core : # of # resources are not ok: [RESOURCE_ID]: wrong resource state: Terminating - Resource scheduled for deletion;] [VCFMS-HEALTH-002]

Environment

• VMware Cloud Foundation (VCF) 9.1

• VCF Identity Broker (vIDB)  9.x

Cause

A manual rename of the vIDB appliance folder in vCenter or within the vIDB appliance created a configuration metadata mismatch. The vIDB cluster metadata retained the legacy folder path, and the VSP controller could not dynamically reconcile this change during the declarative state validation for the upgrade.

Resolution

1. Retrieve the configured folder path on the vIDB 9.0 appliance.

   1. Log in to the vIDB appliance using SSH with the account vmware-system-user.

   2. Elevate to root and enter the password when prompted: sudo su -

   3. Run the following command and record the vIDB virtual machine (VM) folder path: kubectl get pd vmsp-platform -n vmsp-platform -o jsonpath='{.spec.values.provider.vsphere}' | jq 

2. Login to vCenter UI.

3. Navigate to VMs and Templates and search for the vIDB Cluster VMs.

4. Validate that the path matches the output obtained in step 1.c.

5. If the folder path in vCenter differs, manually migrate to vIDB version 9.1 using backup and recovery procedures. Refer method 1: Transition a VCF Identity Broker 9.0.x Instance to the VCF Services Runtime Environment.