NSX Tier-1 is allocated on an Edge that is deleted and realization is failing when trying to relocate it to a different Edge

Products

• VMware NSX

Issue/Introduction

• May see the following java.lang.NullPointerException error in /var/log/proton/nsxapi.log for Tier-1 realization error.

2025-08-14T17:40:49.024Z  INFO providerTaskExecutor-1-128 NetworkProviderNsxT 5225 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] updateAllocationProfile: enableStandbyRelocation false, poolAllocation ROUTING, prevPoolAllocation ROUTING

2025-08-14T17:40:49.077Z ERROR providerTaskExecutor-1-128 PolicyProviderUtil 5225 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500015" level="ERROR" subcomp="manager"] Unexpected exception received during provider invocation.
java.lang.NullPointerException: null
        at com.vmware.nsx.management.edge.cluster.resource.allocation.service.ECResourceAllocationServiceImpl.getAllocationInfo(ECResourceAllocationServiceImpl.java:865) ~[?:?]
        at com.vmware.nsx.management.edge.cluster.resource.allocation.service.ECResourceAllocationServiceImpl.getExistingServiceAllocations(ECResourceAllocationServiceImpl.java:844) ~[?:?]
        at com.vmware.nsx.management.edge.cluster.resource.allocation.service.ECResourceAllocationServiceImpl.setAllocationNode(ECResourceAllocationServiceImpl.java:496) ~[?:?]
        at com.vmware.nsx.management.edge.cluster.resource.allocation.service.ECResourceAllocationServiceImpl.setAllocation(ECResourceAllocationServiceImpl.java:443) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.service.LREdgeClusterAllocationHandler.manualAllocateMember(LREdgeClusterAllocationHandler.java:307) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.service.LREdgeClusterAllocationHandler.manageEdgeClusterAllocationsForTLR(LREdgeClusterAllocationHandler.java:216) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.service.LogicalRouterServiceImpl.manageExternalAllocations(LogicalRouterServiceImpl.java:980) ~[?:?]
        at com.vmware.nsx.management.edge.lrouter.service.LogicalRouterServiceImpl.updateLogicalRouter_aroundBody6(LogicalRouterServiceImpl.java:713) ~[?:?]

• Issue is observed in a Federation environment.
• May have 1 or more Tier-1's stuck with a stale allocation and only Active node, without being able to allocate a new standby.
  • Therefore High-Availability is compromised for the Tier-1.

Environment

VMware NSX

Resolution

This will be fixed in a future version of VMware NSX to prevent the realization failure when the entity tracking allocation (EdgeClusterMemberCapacityPool) on a given Edge is deleted. 

Workaround

• Open a new support case with Broadcom GS for assistance with the Corfu database edit necessary to workaround this on versions prior to the fixed versions.