Unable to configure ESXi host as NSX-T transport node even if transport node configuration does not exist for the host

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:
This error occurs while preparing the ESXi host as an NSX-T transport node and stops the host from being able to be configured

Discovered node with id:e5123e49-27c0-47b6-92f4-8f808532c285:host-67 is already prepared having fabric node id:5b74838b-0edf-41e7-8f46-c74c2795ffe1.(Error code: 400)

Dec 12, 2022, 3:17:02 PM : The operation creating a transport node from the discovered node failed: Discovered node with >id:d8cfd62a-12a6-4259-9cc9-d254a2a5e338:host-3069 is already prepared having fabric node id:4a5827be-540c-4379-bc3a-66d9e7b0f2fd.

Log Location -
/var/log/proton
/var/log/cm-inventory

Environment

VMware NSX-T Data Center 4.x
VMware NSX-T Data Center
VMware NSX-T Data Center 3.x

Cause

Node is holding onto old stale entry

Resolution

reach out to GSS to go over the internal workaround

Workaround:
reach out to GSS to go over the internal workaround

Additional Information

Impact/Risks:
Not able to prepare ESXi host as an NSX-T transport node