"Check for the version sync status of UC on all the MP nodes" FAILURE seen for NSX precheck for upgrade
search cancel

"Check for the version sync status of UC on all the MP nodes" FAILURE seen for NSX precheck for upgrade

book

Article ID: 400665

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Running precheck for an NSX upgrade after the Management Upgrade Bundle (MUB) was uploaded, fails with message:

Check for the version sync status of UC on all the MP nodes. This check ensures the version of UC is in sync across all the MP nodes before starting MP upgrade. FAILURE UC is not updated on node ########-########, ########-########. Please upgrade the UC on these nodes first and ensure the version of UC is same across all MP nodes.

Note: ########-######## refers to a manager name and IP address.

  • The NSX Upgrade page shows a different target version than the one for the MUB uploaded.
  • On each manager checking the /repository/ directory contents, as root user, if upgrading from 4.1.0 to 4.1.2.6, it shows:

ls -l /repository
4.1.0.0.0.21332672
4.2.1.0.0.24304122

Environment

VMware NSX

Cause

The Upgrade coordinator (UC) service on the manager was previously upgraded to a different version, 4.2.1 in our example above, and now you are uploading a new MUB version, 4.1.2.6 in our example above.

Resolution

  1. Identify the manager running the Orchestrator service, as admin user run:
    • get service install-upgrade
  2. The IP address in the result is the manager running the Orchestrator service.
  3. Log in as admin to the Orchestrator manager and run the command:
    • restart service install-upgrade
  4. Once this is complete, go back to the NSX UI:
    • If the new MUB shows as uploaded, click the prepare for install option again.
    • If the new MUB is not present, reupload it and click prepare for install option again.
  5. This will extract the MUB and upgrade the UC service on all managers and sync the repository across the managers.
  6. This can be confirmed by checking the /repository/ directory contents, as root user:
    • ls -l /repository
  7. Now, once the prepare upgrade is complete in the UI, you should see the current version and the new MUB version directories, using our example above it would look like:
    • 4.1.0.0.0.21332672
    • 4.1.2.6.0.0.24723849
  8. You can then proceed with prechecks and upgrade.

Additional Information

Powered by Wolken Software