NSX-T Transport Node Collection display error "One or more relationships exist for object with id TransportNode/<TN-ID>"

Products

• VMware NSX

Issue/Introduction

• During v2T migration, the NSX-T transport nodes displays the following alert: 

"One or more relationships exist for object with id TransportNode/<TN-ID>. Please make the appropriate changes and reapply the configuration." 

• This error will contain the node's appropriate UUID. 
• The TEP interface will not have been created. 
• All the affected hosts will only have vmk0 (standard switch-management). 
• The Transport Node Profile seems to successfully apply, but the N-VDS does not show any connections to the vmnics assigned. 
• The following error will be observed in /var/log/proton/nsxapi.log indicating the Transport Node error :

2022-01-30T09:53:52.388Z INFO http-nio-127.0.0.1-7440-exec-2 ComputeCollectionDeploymentFacadeImpl 14550 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-##########54" subcomp="manager" username="admin"] Performing action [remove_nsx] on compute-collection [########-####-####-####-##########6f:domain-c7]
2022-01-30T09:53:52.505Z INFO http-nio-127.0.0.1-7440-exec-2 NsxComputeCollectionServiceImpl 14550 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Auto 'remove_nsx' validation completed for cluster [########-####-####-####-##########6f:domain-c7]
2022-01-30T14:41:37.866Z ERROR http-nio-127.0.0.1-7440-exec-26 TransportNodeLcmServiceImpl 14550 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP78005" level="ERROR" reqId="########-####-####-####-##########4d" subcomp="manager" username="admin"] Exception thrown during TN delete: One or more relationships exist for object with id TransportNode/########-####-####-####-##########53.

Environment

VMware NSX-T Data Center 3.x

Cause

This issue occurs when an incorrect transport zone is assigned to the logical switch during the migration and an attempt is made to remove the transport node.

Resolution

This is a condition that may occur in a VMware NSX environment.

Workaround

1. Go to System –> Fabric –> Node 
2. Select appropriate VC and then select the Transport Node which has the error.
3. Click Configure NSX (Update dialog box will pop up) -> click next –> No changes –> Click finish.
4. The Transport Node will update and will go to success state as there are no config changes.
5. Once the Transport Node goes to a "success" state, the Transport Node level error should go away.