Removing domain in SDDC Manager fails with error_message=Cannot delete a transport node which is part of TNP applied compute collection

Products

• VMware SDDC Manager

Issue/Introduction

Removing domain workflow fails on Delete Transport Node Configuration from ESXi Host(s)

Description: Delete Transport Node Configuration from ESXi Host(s)

Progress Messages:

Transport node deletion operation failed

Error Message:

Transport node deletion operation failed

Remediation Message: Reference Token: 9TPVT4

Cause:

com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => { messages = [], data = struct => {error_message=Cannot delete a transport node 06ab0c35-8584-4c80-bb86-1167867c1578 which is part of TNP applied compute collection fe3980c3-6e09-466f-80bc-f66419881f91:domain-c10. Please use the object name or UUID in Global Search to find all linked objects., httpStatus=BAD_REQUEST, error_code=9411, module_name=NsxSwitching service}, errorType = INVALID_REQUEST }

Domainmanager.log:

[YYYY-MM-DDTHH:MM:SS] INFO [vcf_dm,391324ee1fe8456b,2d3d] [c.v.v.c.f.p.n.a.DeleteTransportNodes,dm-exec-10] Deletion of transport node by Name: <FQDN> starts with unprepareHost: true

[YYYY-MM-DDTHH:MM:SS] ERROR [vcf_dm,391324ee1fe8456b,2d3d] [c.v.v.c.f.p.n.a.DeleteTransportNodes,dm-exec-10] Exception occurred while deleting the transport node, hence retrying as forced delete, Excepton details: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => { messages = [], data = struct => {error_message=Cannot delete a transport node 06ab0c35-8584-4c80-bb86-1167867c1578 which is part of TNP applied compute collection fe3980c3-6e09-466f-80bc-f66419881f91:domain-c10. Please use the object name or UUID in Global Search to find all linked objects., httpStatus=BAD_REQUEST, error_code=9411, module_name=NsxSwitching service}, errorType = INVALID_REQUEST } at com.vmware.vapi.std.errors.InvalidRequest._newInstance2(InvalidRequest.java:194) at jdk.internal.reflect.GeneratedMethodAccessor2251.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.vmware.vapi.internal.bindings.convert.impl.JavaClassStructConverter.createStructBinding(JavaClassStructConverter.java:275) at com.vmware.vapi.internal.bindings.convert.impl.JavaClassStructConverter.fromValue(JavaClassStructConverter.java:79) at com.vmware.vapi.internal.bindings.convert.impl.JavaClassStructConverter.fromValue(JavaClassStructConverter.java:33) at com.vmware.vapi.internal.bindings.TypeConverterImpl$ValueToJavaVisitor.visit(TypeConverterImpl.java:330) at com.vmware.vapi.bindings.type.ErrorType.accept(ErrorType.java:31) at com.vmware.vapi.internal.bindings.TypeConverterImpl.convertToJava(TypeConverterImpl.java:713) at com.vmware.vapi.internal.bindings.Stub.convert(Stub.java:454) at com.vmware.vapi.internal.bindings.Stub.convertError(Stub.java:471) at com.vmware.vapi.internal.bindings.ResultTranslatingHandle.setResult(ResultTranslatingHandle.java:42) at com.vmware.vapi.internal.bindings.ResultTranslatingHandle.setResult(ResultTranslatingHandle.java:21) at com.vmware.vapi.internal.protocol.client.rest.DefaultRequestExecutorFactory$DefaultHttpResponseHandler.onResult(DefaultRequestExecutorFactory.java:87) at com.vmware.vapi.internal.protocol.client.rpc.http.ApacheClientRestTransport.execute(ApacheClientRestTransport.java:79) at com.vmware.vapi.internal.protocol.client.rest.DefaultRequestExecutorFactory$DefaultRequestExecutor.execute(DefaultRequestExecutorFactory.java:45) at com.vmware.vapi.internal.protocol.client.rest.RestClientApiProvider.invoke(RestClientApiProvider.java:67) at com.vmware.vapi.internal.bindings.Stub.invoke(Stub.java:241) at com.vmware.vapi.internal.bindings.Stub.invokeMethodAsync(Stub.java:191) at com.vmware.vapi.internal.bindings.Stub.invokeMethod(Stub.java:137) at com.vmware.nsx.TransportNodesStub.delete(TransportNodesStub.java:124) at com.vmware.nsx.TransportNodesStub.delete(TransportNodesStub.java:113) at com.vmware.vcf.common.nsxt.sdk.client.connection.TransportNodeOperations.deleteById(TransportNodeOperations.java:125) at com.vmware.vcf.common.nsxt.sdk.client.connection.NsxtManagerTransportNodeOperations.deleteTransportNode(NsxtManagerTransportNodeOperations.java:204) at com.vmware.vcf.common.fsm.plugins.nsxt.action.DeleteTransportNodes.initiateDeleteTransportNode(DeleteTransportNodes.java:234) at com.vmware.vcf.common.fsm.plugins.nsxt.action.DeleteTransportNodes.deleteTransportNode(DeleteTransportNodes.java:192) at com.vmware.vcf.common.fsm.plugins.nsxt.action.DeleteTransportNodes.lambda$execute$0(DeleteTransportNodes.java:131) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) at org.springframework.cloud.sleuth.instrument.async.TraceRunnable.run(TraceRunnable.java:64) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

[YYYY-MM-DDTHH:MM:SS] INFO [vcf_dm,391324ee1fe8456b,2d3d] [c.v.v.c.f.p.n.a.DeleteTransportNodes,dm-exec-10] Deletion of transport node by Name: <FQDN> starts with unprepareHost: false

[YYYY-MM-DDTHH:MM:SS] INFO [vcf_dm,391324ee1fe8456b,d4bc] [c.v.v.c.f.p.n.a.DeleteTransportNodes,dm-exec-13] Deleting Transport Node with Id 421e9546-b231-4fd9-84ec-0de4ac9f09bf configuration from host <FQDN>

[YYYY-MM-DDTHH:MM:SS] INFO [vcf_dm,391324ee1fe8456b,d4bc] [c.v.v.c.f.p.n.a.DeleteTransportNodes,dm-exec-13] isLifecycleManaged: false for the host: <FQDN>

Environment

VCF 4.5.1

Cause

The removing domain workflow cannot remove the transport nodes because it fails to remove the Transport Node Profile.

Resolution

Manually Detach the Transport Node Profile from within the NSX-T UI

1. Access NSX Manager:

Log in to the NSX Manager with administrative privileges using the URL: https://<nsx-manager-ip-address>.

2. Navigate to Host Transport Nodes:

In the NSX-T UI, go to System > Fabric > Nodes > Host Transport Nodes.

3. Select the vCenter Server:

From the "Managed by" drop-down menu, select the vCenter Server that manages the cluster where the Transport Node is located.

4. Select the Cluster:

Select the specific cluster from which you want to remove the Transport Node Profile.

5. Detach the Profile:

Click Actions > Detach TN Profile.

6. Restart the Task:

Once the Transport Node Profile is detached, return to the SDDC Manager UI and restart the task that was failing due to the profile being attached.