Patching NSX failed due to incompatible CPU

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

The failed NSX update results in some edge nodes that are flagged orphaned, which leads to not being able to proceed patching vCenter and ESX hosts.

Seems like edge is experiencing issues moving to post_power_on as seen in the error message:
Edge 4.2.#.#.#.########/Edge/nub/VMware-NSX-edge-4.2.#.#.#.########.nub post power on task failed on edge TransportNode ########-####-####-####-############: clientType EDGE , target edge fabric node id ########-####-####-####-############, return status Issuing post_power_on failed to complete in time

RDSEED is available on the edge node.

Error found in the nsx log:
YYYY-MM-DDTHH:MM:SS ERROR Domain ########-####-####-####-############ with nsx cluster <node_name> is partially upgraded.
YYYY-MM-DDTHH:MM:SS WARN NSX cluster with ID: <node_name>, name: <node_name>, version: {"version":"4.2.#.#.#.########"} is partially upgraded.

Environment

VMware SDDC Manager 5.2.x

Cause

The NSX-T cluster is partially upgraded, which will result to not being able to set a new target version for patch as it will not allow this on SDDC Manager.

Resolution

1. Download the .PUB and .MUB file for 4.2.4.1 from the Broadcom download site, and upload PUB and latter MUB  to the NSX Upgrade UI, and perform the upgrade directly from the NSX Upgrade UI as this will be a standard NSX upgrade workflow.
   
   
2. After the NSX is succesfully upgraded, resync the version to the SDDC Manager using the steps in the KB: Synchronize inventory versions after out-of-band upgrade in a VMware Cloud Foundation Environment.

Additional Information

Synchronize inventory versions after out-of-band upgrade in a VMware Cloud Foundation Environment