NSX Transport Node Profile reports still in use but Applied Clusters details show "No Clusters Available."

Products

• VMware NSX
• VMware vCenter Server

Issue/Introduction

• A vCenter Server cluster of ESX hosts has been prepared for NSX using a Transport Node Profile
• The cluster was prepared with "Activate NSX on DVPGs"
  
• The cluster is subsequently deleted via vCenter actions
• In NSX the Transport Node Profile continues to report it is still assigned to a cluster
  
• Clicking the number indicating where it is used beneath Applied Clusters reveals the assigned cluster is not found:

Environment

• VCF 9.0.2
• NSX 9.0.2
• VC 9.0.2

Cause

NSX requires all actions regarding removing objects start within the NSX GUI or API, and only after NSX has denoted the task is done is it safe to perform work on those objects via vCenter

Resolution

Stale entries left in the Corfu DB need to be deleted manually. 

If you believe you have clusters in this state, please open a Support Request with Broadcom.