Upgrade precheck for VCF Management Components fail due to VMSP version mismatch error
search cancel

Upgrade precheck for VCF Management Components fail due to VMSP version mismatch error

book

Article ID: 458395

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • When attempting to upgrade or patch VCF Management components (such as Identity Broker, Log Management, Salt Master, or other VSP components), the operation fails during the precheck phase.
  • Upon reviewing the precheck workflow subtasks in the VCF Management UI, the failure occurs at the VMSP Platform Version Check.
  • Error Message Example: The system throws an error similar to the following (versions and specific component codes may vary depending on the upgrade path):
    VCF Services Runtime is at version 9.1.0 but this upgrade requires VSP >= 9.1.1 [VCFMS-PRECHECK-VIDB-VMSP-VERSION-001]
  • Even if the VCF services runtime has already been upgraded to the required version, the precheck UI incorrectly suggests the resolution: "Upgrade VSP to the required version before retrying the upgrade."

Environment

  • VCF Operations 9.1.x
  • VCF Services Runtime 9.1.x
  • VCF Management Components 9.1.x

Cause

This issue occurs because the component metadata for the VCF Services Runtime (VSP) has not been appropriately synchronized in the VCF Fleet Lifecycle, causing the system to falsely report a version mismatch. The VCF Management lifecycle engine relies on perfectly synchronized metadata to validate current component versions against upgrade prerequisites. Because the metadata is out of sync (often indicated in the UI by a stale timestamp or Last lifecycle metadata sync time: N/A), the precheck engine incorrectly evaluates the VSP platform as being on an older, incompatible version. This incorrect evaluation creates a hard-block that prevents the target component from upgrading.

Resolution

To resolve this issue, you must manually refresh the component metadata so the lifecycle manager accurately recognizes the current VSP version.
  1. Log in to the VCF Operations UI (https://<VCF_OPS_FQDN_IP>/ui) as admin user.
  2. Navigate to Build > Lifecycle > VCF Management 
  3. On the top right corner, locate the Last lifecycle metadata sync time indicator.
  4. Click the Sync button located directly next to the timestamp to trigger a manual metadata refresh.
  5. Wait for the synchronization to complete. This forces the lifecycle manager to pull and update the accurate version state of the VCF services runtime.
  6. Navigate back to the failed precheck workflow and click Retry.
  7. The VSP Platform Version Check will now pass the prerequisite validation, allowing the component precheck upgrade to proceed normally.

Additional Information

  • Preventative Check: Before initiating any VCF Management component upgrades, it is highly recommended to verify the Last lifecycle metadata sync time in the upper right corner of the Components tab. If the timestamp is exceptionally old or shows as N/A, manually triggering a sync can prevent precheck failures before they occur.
  • Scope: While the exact error code (e.g., VCFMS-PRECHECK-VIDB-...) will change based on the specific component being upgraded (Identity Broker, Log Management, etc.), the underlying metadata synchronization requirement and resolution step remains the same for all VSP component upgrades.