stale IPAddressAllocation which is stuck in "In Progress" state on the NSX UI
search cancel

stale IPAddressAllocation which is stuck in "In Progress" state on the NSX UI

book

Article ID: 423113

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Upon searching the stale IPAddressAllocation on the global search of NSX UI, it will be shown as below

  • The pool member was created from TKG end.
  • Delete using DEL API "https://<nsx-mngr-ip>/api/v1/infra/ip-pools/<pool-name>/ip-allocations/<uuid>" adding "X-Allow-Overwrite: true however issue persists
  • Below logs will be seen under /var/log/syslog

2025-12-02T09:07:50.945Z <nsx-mgr> NSX 6299 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM5008" level="ERROR" subcomp="manager"] Ip Pool identifier is null or empty
2025-12-02T09:07:50.945Z <nsx-mgr> NSX 6299 POOL-MGMT [nsx@6876 comp="nsx-manager" errorCode="MP5008" level="ERROR" subcomp="manager"] Ip Pool Identifier is null
2025-12-02T09:07:50.945Z <nsx-mgr> NSX 6299 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500016" level="ERROR" subcomp="manager"] Service call failed with message Pool identifier is null. and error com.vmware.nsx.management.common.exceptions.InvalidArgumentException: Pool identifier is null.#012#011at com.vmware.nsx.management.idas.ipam.service.IPAMServiceImpl.getPool(IPAMServiceImpl.java:518)#012#011at com.vmware.nsx.management.idas.ipam.service.IPAMServiceImpl.getPoolIfExists(IPAMServiceImpl.java:1132)#012#011at com.vmware.nsx.management.idas.ipam.service.IPAMServiceImpl.release(IPAMServiceImpl.java:752)#012#011at com.vmware.nsx.management.policy.providers.ipam.nsxt.PolicyIpamProviderNsxT.releaseIpOnNsx(PolicyIpamProviderNsxT.java:1316)#012#011at com.vmware.nsx.management.policy.providers.ipam.nsxt.PolicyIpamProviderNsxT.lambda$processIpAddressPoolAllocationDeletion$22(PolicyIpamProviderNsxT.java:1232)#012#011at java.base/java.util.ArrayList.forEach(Unknown Source)#012#011at com.vmware.nsx.management.policy.providers.ipam.nsxt.PolicyIpamProviderNsxT.processIpAddressPoolAllocationDeletion(PolicyIpamProviderNsxT.java:1204)#012#011at com.vmware.nsx.management.policy.providers.ipam.common.PolicyIpamBaseProvider.cleanupObjectsInternal(PolicyIpamBaseProvider.java:178)#012#011at com.vmware.nsx.management.policy.providers.ipam.common.PolicyIpamBaseProvider.handleAtomicPush(PolicyIpamBaseProvider.java:115)#012#011at com.vmware.nsx.management.policy.policyframework.engine.ProviderInvocationTask.handleAtomciPush(ProviderInvocationTask.java:522)#012#011at com.vmware.nsx.management.policy.policyframework.engine.ProviderInvocationTask.innerRun(ProviderInvocationTask.java:268)#012#011at com.vmware.nsx.management.policy.policyframework.engine.ProviderInvocationTask.run(ProviderInvocationTask.java:156)#012#011at 

Environment

VMware NSX 4.x

Cause

Suspected that the pool was deleted before the allocations

Resolution

This needs a corfu edit to cleanup the stale entry. Collect all the 3 NSX Manager nodes support bundles and open a support request with Broadcom