NSX Pre Checks won't start with error "Edge upgrade plan has errors"

Products

• VMware NSX

Issue/Introduction

Uploading a MUB or PUB file to the NSX Upgrade section under the Upgrade Coordinator (UC) node appears to succeed, but presents an error banner reading:
“Edge upgrade plan has # errors”
This message lacks any detailed explanation, and when the user attempts to run upgrade prechecks, the status changes briefly to "In Progress" and then immediately back to "Not Run" without completing the checks.

Example Below:

Upgrade Coordinator version is successfully upgraded to the new version associated with the PUB file.

Restating the install-upgrade service and upgrade-coordinator does not resolve the alarms.

Environment

 

NSX-T Data Center 3.2.3.x

 

Cause

This issue is caused by one or more Edge Node Clusters that were created with Type = “Edge Node” but do not contain any Edge Nodes.

These clusters may still be applied to logical routers (T0/T1) which causes the upgrade coordinator to recognize them during the upgrade planning phase, but cannot proceed due to the missing Edge Node members.

As a result, UC upgrade logic flags these clusters as invalid, leading to the “Edge upgrade plan has errors” message upon uploading the PUB/MUB.

Resolution

To resolve this issue and allow prechecks to proceed:

1. Navigate to:
   System > Fabric > Nodes > Edge Node Clusters

2. Identify Edge Clusters that have no Edge Nodes assigned.

   • These will typically display 0 Edge Nodes under their member count.

3. Cross-reference these empty clusters with your routing configuration:

   • Check T1 or T0 logical routers and remove the affected cluster from their configuration.

4. After disassociating the empty cluster(s), delete the clusters from the environment entirely.

5. Once the empty clusters have been removed, retry the PUB/MUB upload (if necessary).

6. The Edge upgrade plan errors should now be cleared and the prechecks should execute successfully.

Note:
The UI banner message will specify the number of errors (e.g., “Edge upgrade plan has 2 errors”). Use this to confirm how many clusters need to be reviewed and potentially removed.

Additional Information

 

No CLI/API steps are typically required for this fix; it can be completed fully via the NSX UI.

If the issue persists after cluster deletion, consider restarting the install-upgrade service on the UC node and reattempting upload.