NSX upgrade pre-check fails while uploading pub file with an Error : Upgrade-coordinator upgrade failed. error - repository sync status is not success on node.

Products

• VMware NSX

Issue/Introduction

• While initiating the upgrade precheck, below error is thrown while uploading the .pub file
  
  Error: upgrade-coordinator upgrade failed. error - repository sync status is not success on node #.#.#.# ,#.#.#.#,#.#.#.#. please ensure repository sync status is sucess on all MP nodes before proceeding.
You can check the synchronization status on 'System' - 'Appliances' page under view details tab.




• Cluster shows DEGRADED as REPO_SYNC service shows  FAILED on one or two of the NSX Manager nodes 

         

         

• Below errors are seen in /var/log/proton/nsxapi.log 

2026-06-24T15:02:49.660Z  INFO NSXUcUpgradeService-1-1 UcRetryUtils 1954778 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Method GetRepoSyncResult executed successfully and answer received on retry 1.

2026-06-24T15:02:49.660Z  INFO NSXUcUpgradeService-1-1 NSXRepoSyncUcUpgradeStep 1954778 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Repo sync completed for node RepoSyncStatusReportDto{status='FAILED', statusMessage='', failureMessage='Unable to connect to File /repository/<NSX-Version>/UC/jre/upgrade-coordinator-tomcat-wrapper-jdk11.conf on source ####.###.###.###.####.###. Please verify that file exists on source and install-upgrade service is up.', failureCode='21057'} . Skipping it from progress calculation step.

2026-06-24T15:02:49.660Z  INFO NSXUcUpgradeService-1-1 NSXRepoSyncUcUpgradeStep 1954778 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Updating the Uc Upgrade status with progress messages : [[#.#.#.#] Collecting the information about files to synchronize] and percentage : 40

Environment

VMware NSX

Resolution

To resolve the issue, follow the steps below.

1. On each VMware NSX Manager Appliance, check which directories are present in the /repository directory by running below  command as a root user.    

    ls -l /repository

2. You may see both the from and to version directories; that is, a directory with the previous VMware NSX version as its name and another directory with the current VMware NSX version as its name:
   

   drwxrwx--- 7 uuc grepodir 4096 <date> 4.2.1.0.####
   drwxrwx--- 7 uuc grepodir 4096 <date> 4.2.2.0.####

3. On the affected NSX node(s), the target VMware NSX version directory may be missing from the /repository directory.
   
   
4. Copy the /repository directory from a healthy NSX Manager node to the affected NSX Manager node(s) using the scp command..
   

   scp -r /repository <remote User>@<IP of Remote Server>:/

   Example command:
# scp -r /repository root@#.#.#.#:/
   The above command copies the /repository directory recursively to the root directory (/) of host #.#.#.#


5. Then, verify the ownership, group, and permissions. Ensure that the entire /repository directory, including all subdirectories and files, is owned by the uuc user and the grepodir group.
   
   • Run the following command in the SSH of the affected NSX Manager node(s) to recursively set the ownership: 
     

     chown -R uuc:grepodir /repository

   • Run the following command in the SSH of the effected NSX Manager nodes to set the required permissions: 
     

     chmod -R 770 /repository 

      

6. Once completed , log in to NSX UI and click the Resolve button next to the Failed status of the REPO_SYNC Service.
7. After the service status changes to UP , retry uploading the .pub file and proceed with the upgrade.

Additional Information

After replacing Managers or while running Upgrade prechecks, Repo_Sync is Failed