Resolving the "Update is not staged" Loop During VMware vCenter Patch or Update

Products

• VMware vCenter Server

Issue/Introduction

This article provides detailed steps to resolve the issue where the VMware vCenter Server Appliance (VCSA) upgrade process is stuck in an "Update is not staged" loop. This issue occurs when discrepancies or missing files prevent the update from being properly staged, causing the VAMI (vCenter Appliance Management Interface) to continue showing the old version, despite the update logs indicating success.

Environment

 

• Product: VMware vCenter Server Appliance (VCSA)
• Versions: All versions affected by this issue 6.7,7.x, 8.x

Cause

The issue is typically caused by discrepancies or missing files during the update staging process. This can happen due to incomplete downloads, corrupted files, or issues during the staging phase of the update.

Resolution

To resolve this issue, follow these steps:

1. Stop the Staging Process

• SSH into the vCenter Server Appliance.
• Run the following command to stop the current staged update:
  bash

   

  software-packages unstage

2. Stop the Application Manager Services

• Stop the application manager services by executing:
  bash

   

  service-control --stop applmgmt

3. Clear Update and Staging Files

• Clear the update and staging files to remove any potential corrupted or incomplete files:
  bash

   

  rm -rf /storage/core/software-update/updates/* rm -rf /storage/core/software-update/stage/* rm -rf /storage/db/patching.db

4. Move Configuration Files

• Move the configuration files that could be causing the issue:
  bash

   

  mv /storage/core/software-packages/staged-configuration.json /storage/core mv /etc/applmgmt/appliance/software_update_state.conf /storage/core

5. Restart the Application Manager Services

• Restart the application manager services using:
  bash

   

  service-control --start applmgmt

6. Verify the Version

• Run the following command to verify the VAMI version:
  bash

   

  cat /etc/issue
  • If the VAMI still shows the old version but rpm -qa shows the latest patch, proceed to the next step.

7. Update the Configuration File

• Backup the current update configuration file:
  bash

   

  cp /etc/applmgmt/appliance/update.conf /etc/applmgmt/appliance/update.conf.bak
• Edit the /etc/applmgmt/appliance/update.conf file and manually update the version and build fields to match the latest build.

Validation

After performing the above steps, the VAMI should correctly reflect the latest version, and the "Update is not staged" loop should be resolved. The update process can then proceed as expected.

Additional Information

Related Knowledge Base Articles:

 Resolving issues with "Stage path file doesn't exist" or package discrepancies. checks.https://knowledge.broadcom.com/external/article/318581/update-from-vcenter-70-update-3-to-u3a-f.html

Workarounds for vCenter Server update failures related to pre-installation checks.https://knowledge.broadcom.com/external/article?articleNumber=313301