VCFMS-HEALTH-002 - "Package Deployment Suspended" failure during prechecks for vIDB and VCF Automation when upgrading to VCF 9.1

Products

• VCF Operations

Issue/Introduction

When attempting to upgrade VMware Cloud Foundation (VCF) Identity Broker (vIDB) or VCF Automation from 9.0.2 to 9.1.x, pre-check or upgrade tasks are failing with errors like:

Health Check Error [platform-package-core : 1 of 1 resources are not ok: vmsp-platform: wrong resource state: InProgress - package deployment suspended;] [VCFMS-HEALTH-002]

Platform Health Check Error [vidb-synthetic-checker-vidb-external-vidb-package-core : 1 of 1 resources are not ok: vidb: wrong resource state: InProgress - package deployment suspended;] [VCFMS-HEALTH-002]

Platform Health Check Error [platform-statefulsets-core : 1 of 10 resources are not ok: seaweedfs-volume: wrong resource state: InProgress - Ready: 2/3;] [VCFMS-HEALTH-002]

Environment

• VMware Cloud Foundation 9.0.2
• VMware Cloud Foundation 9.1.x

Cause

The VCF Management Services Platform (VMSP) detects that the package deployment for core infrastructure (such as vmsp-platform or seaweedfs-volume) is in a suspended or inconsistent state. This can be the result of:

• Stale 9.0.2 legacy components (Automation or Identity Broker) remaining in the VMSP database, thus preventing the 9.1 import.
• The vmware-system-user password having expired or being incorrect, hence preventing VCF Operations from communicating with the VMSP control plane.
• Critical stateful sets (e.g., seaweedfs-volume) failing to reach a 3/3 ready state due to datastore or networking issues.

Resolution

Broadcom Engineering are investigating.
Contact Broadcom support for assistance with solving the issue.