'No route to host (Host unreachable)' errors in VCD Logs due to decommissioned NSX-V manager remaining registered

Products

• VMware Cloud Director

Issue/Introduction

VMware Cloud Director (VCD) cells are continuously generating warning messages related to an unreachable NSX-V Manager. These repeated entries are cluttering the log files with No route to host errors.

An example of the error found in the log file located at /opt/vmware/vcloud-director/logs/vcloud-container-debug.log is shown below:

2025-04-17 13:32:10,954 | WARN unable to determine primary nsx manager <nsx manager fqdn> primary nsx manager.
network trig-web-activity-pool-7007 | primarynsxmanager client org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://<nsx-manager-fqdn>/api/2.0/universalsync/configuration/role": No route to host (Host unreachable); nested exception is java.net.NoRouteToHostException: No route to host (Host unreachable)java:91)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:791)

Environment

VMware Cloud Director 10.x

Cause

The NSX-V Manager was decommissioned without being properly unregistered from VMware Cloud Director. As a result, VCD is still attempting to contact the now-unreachable NSX Manager, leading to repeated NoRouteToHostException errors in the logs.

Resolution

1. Unregister the NSX-V Manager using how to unregister NSX-V Manager.
2. Validate removal via the VCD provider UI:
3. Navigate to: Resources → Infrastructure Resources → NSX Managers
4. Ensure the decommissioned NSX-V Manager is not listed.