Repo_sync status fails on NSX Managers while running pre-checks for NSX Manager upgrade from 4.1.0.2 to 4.2.1.3
search cancel

Repo_sync status fails on NSX Managers while running pre-checks for NSX Manager upgrade from 4.1.0.2 to 4.2.1.3

book

Article ID: 392736

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

NSX Manager upgrade pre-check fails with below errors on NSX GUI:

  • Failed to execute check for the version sync status of UC on all the MP nodes
  • Repository sync is not complete on all 3 NSX managers as it was showing failed on NSX GUI:

 

 

  • Following log snippets are seen in var/log/nsxapi.log:
####-##-##T##:##:##.###  INFO http-nio-127.0.0.1-7440-exec-10 RepositoryServiceImpl 4598 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-###########" subcomp="manager" username="uproton"] Repo-sync status for <IP of node> node is FAILED.

Environment

NSX 4.1.0.2

Cause

When NSX Managers are upgraded from one NSX version to another, the /repository folder on the Orchestrator node should have folders of both current (from) version and the target (to) versions.
For example, if NSX managers are to be upgraded from 4.1.0.2 to 4.2.1.3, then /repository folder on Orchestrator node should contain folders of both 4.1.0.2 and 4.2.1.3 NSX versions.

Resolution

  • Follow KB:  After replacing Managers or while running Upgrade prechecks, Repo_Sync is Failed to deploy both MUB files in /repository of Orchestrator node and then click resolve in "repo_sync" on Orchestrator node in NSX GUI.
  • Once the repo_sync is successful on Orchestrator node, click resolve repo_sync on other two NSX managers in NSX GUI so that /repository folder on NSX managers syncs with Orchestrator node. 

Additional Information

Powered by Wolken Software