Following log lines observed in NSX Manager logs which identify the issue:
/var/log/upgrade-coordinator/upgrade-coordinator.log:
ERROR WrapperStartStopAppMain UpgradePlanSynchronizationServiceImpl 3368501 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30080" level="ERROR" subcomp="upgrade-coordinator"] Sync Plan Failed. Ignoring this exception .com.vmware.nsx.management.upgrade.exceptions.InvalidPlanException: null
/var/log/proton/nsxapi.log:
INFO http-nio-127.0.0.1-7440-exec-37886 UI_LOG 76968 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="0ecdd677-####-####-####-############" subcomp="manager" username="[email protected]"] {"user":"[email protected]","message":"Api Errors->","messageData":{"headers":{"normalizedNames":{},"lazyUpdate":null},"status":500,"statusText":"Internal Server Error","url":"https://test.example.com/api/v1/upgrade/status-summary","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://test.example.com/api/v1/upgrade/status-summary: 500 Internal Server Error","error":{"httpStatus":"INTERNAL_SERVER_ERROR","error_code":30479,"module_name":"upgrade-coordinator","error_message":"Error: Reboot less upgrade cannot be disabled for vSphere Lifecycle Managed cluster '5d59364f-####-####-####-############:domain-c##'. (Error code: 30479)","error_data":{"status":500}}},"level":"Error","browser":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36 Edg/136.0.0.0","time":"Wed May 14 2025 22:18:29 GMT-0500 (Central Daylight Time)","location":"/app/system/home/upgrade/home/summary"}
VMware NSX
This issue occurs when user migrates from non-vLCM cluster to vLCM Cluster along with remediation post VC upgrade - syncing of Upgrade Plan fails.
This is a known issue affecting VMware NSX. There is currently no resolution
Workaround
Run the following command from the NSX manager CLI (while logged in as root):
curl -ku 'admin' -X POST 'https://localhost/api/v1/upgrade/plan?action=reset&component_type=HOST'
Note: Above command needs to be run on all Manager nodes in the Cluster