repo_sync status is not success on node ##.##.##.##
search cancel

repo_sync status is not success on node ##.##.##.##

book

Article ID: 413924

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Begin upgrade progress workflow reports 'Repository Sync status is not success on node ##.##.##.##'.
  • UI reports the Repo_Sync status 'Failed'
  • The resolve workflow didn't help.
  • We could notice "metadata does not exist, cannot populate metadata" from the upgrade-coordinator logs 

    2025-10-06T10:29:15.411Z NSXMGR03.local NSX 3010704 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Looking for metadata for bundle version 4.2.3.1.0.24954727 (/repository/4.2.3.1.0.24954727/metadata)

    2025-10-06T10:29:15.411Z NSXMGR03.local NSX 3010704 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Loading metadata from /repository/4.2.3.1.0.24954727/metadata

    2025-10-06T10:29:15.411Z NSXMGR03.local  NSX 3010704 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="upgrade-coordinator"] Loading metadata from /repository/4.2.3.1.0.24954727/metadata into memory

    2025-10-06T10:29:15.412Z NSXMGR03.local  NSX 3010704 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30037" level="ERROR" subcomp="upgrade-coordinator"] Metadata directory /repository/4.2.3.1.0.24954727/metadata does not exist, cannot populate metadata

    2025-10-06T10:29:15.450Z NSXMGR03.local  NSX 3010704 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30037" level="ERROR" subcomp="upgrade-coordinator"] Could not populate metadata. Exception : Metadata directory /repository/4.2.3.1.0.24954727/metadata does not exist.

  • The particular node repository folder doesn't have the target version folder.
  • The manager node was not redeployed.

Environment

VMware NSX.

Cause

The target version hasn't been present in the repository folder, which led to the repository sync failing.  

Resolution

Copy the repository folder contents from the node that already has it.

Additional Information

If the manager was redeployed, follow the KB - https://knowledge.broadcom.com/external/article/322436/  

Similar Repo_sync issue KB reference 
 https://knowledge.broadcom.com/external/article?articleNumber=392736 
 https://knowledge.broadcom.com/external/article?articleNumber=406291 
 https://knowledge.broadcom.com/external/article?articleNumber=412317 

If you are contacting Broadcom support about this issue, please provide the following:

  • The current version of NSX.
  • The version being upgraded to.
  • The state of the REPO_SYNC on all three managers

Handling Log Bundles for offline review with Broadcom support