Cannot upgrade ESXi servers, fails with Unexpected error while upgrading upgrade unit: can't parse argument number: <EOL> "httpStatus" : "BAD_REQUEST"
Article ID: 415943
Updated On:
Products
Issue/Introduction
NSX Host Upgrade Fails, and the upgrade status is Not Started.
Certificates were recently replaced after which compute manager was in down state.
Environment
VMware NSX
Cause
Due to a recent certificate replacement, there is a thumbprint mismatch between the Compute Manager and NSX. As a result, the Compute Manager status appears as Down in NSX UI, which prevents the upgrade process from proceeding and triggers the above error.
Resolution
To resolve the Compute Manager “Down” state caused by a thumbprint mismatch after a vCenter Server certificate replacement, follow the below KB article.
After the vCenter Server certificate is replaced, the compute manager connection is "Down" in the NSX UI
If the issue persists even after applying the workaround mentioned in the above Knowledge Base article, please contact the Broadcom Support Team following KB Creating and managing Broadcom cases for further assistance
Additional Information
A similar issue — where the vCenter VMDIR service is in Read-Only Mode — along with its resolution, is documented in the below Knowledge Base article.
NSX Host Upgrade Fails immediately with error "Unexpected error while upgrading upgrade unit: can't parse argument number: <EOL>"
Feedback
