NSX 4.2.3.1 to 4.2.4.1 Upgrade Paused due to UC Version Sync Failure and HTTPS Cluster Group Degradation
Article ID: 450651
Updated On:
Products
Issue/Introduction
During a planned upgrade of a VMware NSX environment to 4.2.4.1, the upgrade process pauses. Upgrade Coordinator (UC) pre-checks consistently fail with the following error:
"MP Check for the version sync status of UC on all the MP nodes. FAILURE Failed to execute Check for the version sync status of UC on all the MP nodes. Failed to execute method GetStatusSummary. Some appliance components are not functioning properly."
When checking the cluster state, the HTTPS cluster group is reported as DEGRADED, with upgraded nodes showing as DOWN while the non-upgraded node remains UP. The upgraded nodes report the expected 4.2.4.1 version but fail to process API service commands.
When checking the Alarms, page, you see
"Log messages to logging server <FQDN>@<Port Number>@TCP/UDP cannot be delivered possibly due to an unresolvable FQDN"
In syslog log file you may see
2026-07-22T12:59:08.423Z <LOG SERVER FQDN> NSX 397657 - [nsx@6876 comp="global-manager" subcomp="node-mgmt" username="root" level="ERROR" errorCode="NOD101"] traceback#012Traceback (most recent call last):#012 File "/opt/vmware/nsx-node-api/bin/python/management_api/webserver/nvpapi.py", line 498, in #012 main()#012 File "/opt/vmware/nsx-node-api/bin/python/management_api/webserver/nvpapi.py", line 341, in main#012 handler.initialize_pre_start(config)#012 File "/opt/vmware/nsx-node-api/bin/python/management_api/napi/root/node/services/syslog/exporters.py", line 1994, in initialize_pre_start#012 if not _update_firewall_rules_for_all_exporters():#012 File "/opt/vmware/nsx-node-api/bin/python/management_api/napi/rest_routine_roothelper.py", line 192, in new_fn#012 raise return_exception#012socket.gaierror: [Errno -2] Name or service not known
Environment
- NSX 4.2.4.1
Cause
This issue is caused by a race condition during the NSX 4.2.4.1 upgrade. A regression introduces an unhandled socket.gaierror (Name or service not known) during the management plane service initialization, specifically when the node attempts to resolve an unreachable FQDN for a configured logging server. This crash causes the nsx-mp-api-server to fail on boot, leading to the cascade of HTTP API failures and the subsequent paused upgrade state.
Resolution
The service failure is resolved by ensuring the logging server FQDN is reachable or by migrating the configuration to use a static IP address. For full technical remediation steps and cleanup procedures, refer to:
Additional Information
For more information on the log server alarm, please refer to:
Feedback
