Upgrade precheck failed for vIDB 9.1 to 9.1.1
search cancel

Upgrade precheck failed for vIDB 9.1 to 9.1.1

book

Article ID: 458191

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

Upgrade of VMware Cloud Foundation (VCF) from version 9.1 to 9.1.1 encounters a failure during the Identity Broker (vIDB) Database Upgrade Precheck with the generic error code [VCFMS-PRECHECK-GENERIC-001].

Database Upgrade Precheck 
An unknown error occurred. Please retry the operation or contact support if the issue persists. [VCFMS-PRECHECK-GENERIC-001].

Environment

VMware Identity Broker 9.1

Cause

A leftover secret (vidb-import-data in the vmsp-platform namespace) from a prior 9.0 to 9.1 vIDB migration is retained. The 9.1 to 9.1.1 patch workflow detects this stale secret and imports an outdated source-cluster kubeconfig. Consequently, the Postgres Upgrade Precheck initiates a blue/green deployment path and attempts to query the non-existent or inaccessible legacy source cluster for the Spilo leader pod, triggering the generic precheck failure.

Resolution

  1. Locate the secrets and note their namespaces (commonly in the component or vmsp-platform namespace)
    kubectl get secret -A | grep -E "vidb-import-data|vcfa-import-data"

  2. Export a backup of the stale secret:
    kubectl get secret vidb-import-data -n vmsp-platform -o yaml > /root/vidb-import-data.bak.yaml

  3. Remove the stale secret from the Kubernetes cluster:
    kubectl delete secret vidb-import-data -n vmsp-platform

  4. Retry the vIDB upgrade precheck from the VCF management interface.