NSX Manager displays an "Upgrade in progress" notification even though the upgrade was previously completed. This typically occurs after the Upgrade Coordinator service restarts or manager nodes are rebooted.
The NSX-UI indicates the upgrade is not complete.
System > Fabric > Hosts, one or more hosts show a status of DOWN./var/log/upgrade-coordinator/upgrade-coordinator.log contains the following entry: INFO ... subcomp="upgrade-coordinator"] Group: ####-####-####:domain-####, status: PAUSED, unit count: 6, failed count: 0, % complete: 83.0.A software processing issue causes host upgrade status to regress if post-upgrade checks fail after the Upgrade Coordinator JVM restarts. This happens if hosts were removed from vCenter, experienced hardware failure, or became unresponsive after the upgrade was originally finished.
Fixed in NSX 4.1.2.5, 4.2.0, and higher. See to download this release.
Subscribe to this article to be updated on fix status: .
Workaround:
Navigate to System > Upgrade > Hosts in the NSX Manager UI.
Identify which hosts are in a Failed post-check state.
Verify the status of these hosts in System > Fabric > Hosts and within the vSphere Client.
Resolve any connectivity or "Not Responding" issues for the identified hosts.
If the host no longer exists in vCenter or cannot be recovered, remove it from the cluster and delete it from NSX via API: DELETE "/api/v1/transport-nodes/<transport-node-id>?force=true&unprepare_host=false".
Refresh the System > Upgrade page to sync the status.
For instructions on collecting logs for further troubleshooting, see .