"Collecting the information about files to synchronize"
# curl -k -H "Content-Type:application/json" -u admin -X GET https://localhost/api/v1/cluster/nodes/<manager-node-uuid>/repo_sync/status
{ "status" : "FAILED",
"status_message" : "Collecting the information about files to synchronize",
"failure_message" : "",
"failure_code" : 0
}
# curl -k -H "Content-Type:application/json" -u admin -X GET https://localhost/api/v1/cluster/nodes/<manager-node-uuid>/repo_sync/status
{ "status" : "in progress",
"status_message" : "Collecting the information about files to synchronize",
"failure_message" : "",
"failure_code" : 0
}
/var/log/proton/nsxapi.log
shows the repo sync failure occurs as reverse DNS alias #.#/#.#.#.#.in-addr.arpa
fails to resolved ip address and connection timeout for repository url.2025-07-27T22:13:57.523Z WARN DnsLookupProviderImpl - Fail to get IP address from FQDN #.#/#.#.#.#.in-addr.arpa
2025-07-26T22:07:04.104Z INFO RepoSyncFileHelper - curl_wrapper: (7) Connection timed out URL: https://
#.#/#.#.#.#
.in-addr.arpa:443/repository/...
VMware NSX
VMware NSX-T Datacenter
DNS reverse lookup configured with CNAME alias (#.#/#.#.#.#.in-addr.arpa),
where CNAME alias failed to resolve ip-address.
To fix the issue, ensure that forward and reverse DNS lookups are working properly for all three NSX Manager nodes.
Forward lookup:dig <FQDN of Manager> +short
==> Should return the IP address of the Manager
Reverse lookup:dig -x <IP of Manager> +short
==> Should return fully qualified domain name of the Manager
If reverse DNS is configured with CNAME alias instead of direct PTR record. Make sure forward lookup of alias resolve the ip-address.
dig -x <IP of Manager> +short
(
#.#/#.#.#.#.in-addr.arpa
← alias configured<FQDN of Manager>
Forward lookup of alias:
dig <alias-name> +short
==> Should return the IP address