Unable to remove a created Transport Zone. Error: Unable to delete TransportZone TransportZone/(UUID) because there are # TransportNode(s) on this Zone. Please use the object name or UUID in Global Search to find all linked objects. (Error code: 8102)
search cancel

Unable to remove a created Transport Zone. Error: Unable to delete TransportZone TransportZone/(UUID) because there are # TransportNode(s) on this Zone. Please use the object name or UUID in Global Search to find all linked objects. (Error code: 8102)

book

Article ID: 392222

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Attempting to delete unused TransportZone results in Error: Unable to delete TransportZone TransportZone/(UUID) because there are # TransportNode(s) on this Zone. Please use the object name or UUID in Global Search to find all linked objects. (Error code: 8102):
  • Using API call to delete unused TransportZone results in the same error:

  • Searching the object name or UUID in Global Search shows no linked objects:
  • NSX Manager log under /var/log/proton/nsxapi.log shows the same error seen from NSX UI while attempting to delete the TransportZone associated with TransportNode(s):

<timestamp> ERROR http-nio-127.0.0.1-7440-exec-2918 TransportZoneServiceImpl 930534 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8102" level="ERROR" reqId="<UUID-redacted>" subcomp="manager" username="<username-redacted>"] Unable to delete TransportZone TransportZone/<UUID-redacted> because there are 1 transport nodes on this zone.

Environment

VMware NSX

Cause

The TransportZone delete workflow references a section of the TransportNode configuration in the HostTransportNode database table that is no longer used. 

Steps to reproduce:

  • Create a TransportNodeProfile (TNP) with a TransportZone (TZ).
  • Edit the TNP and add a new TZ. Save.
  • Edit the TNP again and delete the original TZ. Save.
  • This causes the TransportZone delete process to refence a section of the TransportNode configuration that is no longer used. 

Resolution

Issue has been resolved in NSX 4.2.3 and 9.0.1

Workaround:

  • Update TransportNodeProfile with correct TransportZones and reapply changes to correct it or click "resolve" if "mismatch" is shown for Transport Node from NSX UI.
  • Re-install NSX VIBs on the host(s) in question still associated with the TransportZone that needs to be deleted.
  • If the TransportNode(s) associated with the TransportZone in question are not identifiable in the NSX UI, then please collect the information outlined in the Additional Information section below and open a technical support case with Broadcom Support for further investigation and refer to this KB article.

Additional Information