NSX Manager Upgrade Rollback Failure Due to Missing Rollback Bundle in Repository (NSX 4.2.x)
search cancel

NSX Manager Upgrade Rollback Failure Due to Missing Rollback Bundle in Repository (NSX 4.2.x)

book

Article ID: 452505

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

During an NSX Manager upgrade from 4.2.3 to 4.2.4.1, the upgrade may fail with the error: "Failed to handover upgrade control to another node." Attempting a rollback subsequently fails with: "Cannot start rollback - Version <version_number> is not available on node." This issue occurs when the node repository lacks the required rollback bundle, preventing the system from identifying the version to which it should revert.

Environment

  • VMware NSX 4.2.x
  • NSX Manager nodes in a cluster (Upgrade Coordinator enabled)

Cause

  • Upgrade failure: "Failed to handover upgrade control to another node."
  • Rollback failure: "Cannot start rollback - Version <version_number> is not available on node."
  • Repository check reveals the missing rollback directory in /image/.

Cause A repository synchronization failure occurs during the upgrade process where the Upgrade Coordinator fails to extract the rollback bundle on one or more manager nodes. Consequently, the node lacks the metadata and files required to trigger a rollback.

Resolution

  1. Verify the current version and repository contents by running: cat /repository/current_version ls -l /image/
  2. If the rollback directory VMware-NSX-unified-appliance-<version>-rollback is missing on the affected node, do not manually copy files. This requires administrative intervention to synchronize the repository.
  3. Gather the following logs for Broadcom Support:
    • /var/log/upgrade-coordinator/upgrade-coordinator.log
    • /repository/current_version
    • ls -l /image/ output
  4. Open a support request with Broadcom Support, providing the bundle logs mentioned above.

Additional Information