When a Transport Node force delete is executed, the host transport node gets stuck in an uninstalling state.

Products

• VMware NSX

Issue/Introduction

• When Transport Node force delete is tried from NSX UI and DELETE API calls were performed, host entry was not removed from NSX
• You see a message similar to the following:
  
  Error: Principal <user> with role <role> attempts to delete or modify an object of type HostTransportNode it doesn't own. (createUser=nsx-t-superuser, allowOverwrite=null) (Error code: 289)


• You see messages similar to the following in nsxapi.log:
  
  

  2023-12-27T05:50:00.395Z ERROR providerTaskExecutor-47 OwnershipValidatorImpl 4644 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP289" level="ERROR" subcomp="manager"] Principal 'nsx_policy' with role '[]' attempts to delete or modify an object of type nsx$TransportNodeState it doesn't own. (createUser=nsx-t-superuser, allowOverwrite=null)
  2023-12-27T05:50:00.395Z ERROR providerTaskExecutor-47 TxnContext 4644 TX Abort merge: nsx$TransportNodeState
  com.vmware.nsx.management.container.exceptions.InvalidOwnerException: null
          at com.vmware.nsx.management.protection.OwnershipValidatorImpl.checkCallerIsOwner(OwnershipValidatorImpl.java:62) ~[?:?]
          at com.vmware.nsx.persistence.UfoTxn.checkOwnership(UfoTxn.java:885) ~[?:?]
          at com.vmware.nsx.persistence.UfoTxn.access$100(UfoTxn.java:44) ~[?:?]
          at com.vmware.nsx.persistence.UfoTxn$MergeCallbackImpl.doMerge(UfoTxn.java:641) ~[?:?]
          at org.corfudb.runtime.collections.TxnContext.merge(TxnContext.java:254) ~[?:?]
          at com.vmware.nsx.persistence.UfoTxn.putRecord(UfoTxn.java:569) ~[?:?]
          at com.vmware.nsx.persistence.UfoTxn.putRecord(UfoTxn.java:141) ~[?:?]
          at com.vmware.nsx.management.container.dao.IdentifiableProxyObjectDao.update(IdentifiableProxyObjectDao.java:289) ~[?:?]
          at com.vmware.nsx.management.container.dao.IdentifiableProxyObjectDao.update(IdentifiableProxyObjectDao.java:251) ~[?:?]
          at com.vmware.nsx.management.switching.infrastructure.dao.TransportNodeStateDaoHelper.update(TransportNodeStateDaoHelper.java:52) ~[?:?]
          at com.vmware.nsx.management.policy.providers.transportnode.L2TransportNodeProviderNSXT.lambda$cleanupObjects$0(L2TransportNodeProviderNSXT.java:172) ~[?:?]
          at java.util.HashMap.forEach(HashMap.java:1290) ~[?:1.8.0_342]
          at com.vmware.nsx.management.policy.providers.transportnode.L2TransportNodeProviderNSXT.cleanupObjects(L2TransportNodeProviderNSXT.java:161) ~[?:?]
          at com.vmware.nsx.management.policy.policyframework.engine.ProviderInvocationTask.handleMarkedForDelete(ProviderInvocationTask.java:367) ~[?:?]
          at com.vmware.nsx.management.policy.policyframework.engine.ProviderInvocationTask.run(ProviderInvocationTask.java:293) ~[?:?]
          at com.vmware.nsx.management.common.executor.TaskExecutorImpl$TaskWrapper$1.run(TaskExecutorImpl.java:238) ~[?:?]
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_342]
          at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_342]
          at com.vmware.nsx.management.common.executor.TaskExecutorImpl$TaskWrapper.run(TaskExecutorImpl.java:271) ~[?:?]
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_342]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_342]
          at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_342]
  2023-12-27T05:50:00.395Z  WARN providerTaskExecutor-47 L2TransportNodeProviderNSXT 4644 POLICY [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Exception occurred in TN realization [com.vmware.nsx.management.switching.common.exceptions.SwitchingException: Error in updating TN state]
  2023-12-27T05:50:00.395Z  INFO providerTaskExecutor-47 ProviderInvocationTask 4644 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Invoked cleanup on the provider for the objects {HostTransportNode=[/infra/sites/default/enforcement-points/default/host-transport-nodes/a1b2c3d4-####-####-####-k2l3m4n5o6p7]}

Environment

VMware NSX-T Data Center
VMware NSX

Resolution

This issue is resolved in VMware NSX 3.2.4
This issue is resolved in VMware NSX 4.2.0