Error: "Unable to parse Uniform Resource Name (URN) ID: '<segment_id>'." when adding an Edge Gateway to Data Center Group

Products

• VMware Cloud Director

Issue/Introduction

• Adding an Edge Gateway to a Data Center Group in VMware Cloud Director (VCD) fails.
• In the VCD Tenant Portal the Networking > Data Center Groups > open the Data Center Group > Edge Gateway > Add Edge action fails with an error of the form:
  
  [ #########-####-####-####-############ ] Unable to parse Uniform Resource Name (URN) ID: '<segment_id>'.
  
  
• The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the VCD Cells shows errors of the form:
  
  | DEBUG    | pool-jetty-#             | NsxTOrgVdcEdge                 | Validation error occurred when increasing the scope of Edge Gateway <edge_gateway_name> to VDC Group (com.vmware.vcloud.entity.vdcGroup:#########-####-####-####-############). | requestId=#########-####-####-####-############,request=PUT https://<vcd_address>/cloudapi/1.0.0/edgeGateways/urn:vcloud:gateway:#########-####-####-####-############,requestTime=#############,remoteAddress=#.#.#.#:#####,userAgent=Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:145.0) Gecko/20100...,accept=application/json;version 40.0.0-alpha
com.vmware.vcloud.api.presentation.service.BadRequestException: Unable to parse Uniform Resource Name (URN) ID: '<segment_id>'.
        at com.vmware.ssdc.backendbase.util.EntityRefUtil.validateIdIsUrn(EntityRefUtil.java:317)
        at com.vmware.ssdc.backendbase.util.EntityRefUtil.createEntityRefFromUrn(EntityRefUtil.java:301)
        at com.vmware.vcloud.networking.model.edge.nsxt.NsxTEdge.lambda$validateNextHopsInExternalNetworkScope$3(NsxTEdge.java:841)
  
  
• The NSX Segment ID in the error maps to a valid Routed Organization VDC Network created in VCD.
• There is a Static Route on the Edge Gateway that was created in the VCD UI scoped to this Routed Organization VDC Network.
• VCD is connected to multiple vCenter Servers that share a single NSX Manager.
• There are multiple Provider VDCs that use the same NSX Manager, but different vCenter Servers.
• The Network Pool used to create the Routed Organization VDC Network connected to the Edge Gateway is backed by a Transport Zone in NSX that spans multiple yCenter Servers.

Environment

VMware Cloud Director 10.6.1.x

Cause

When attempting to add an Edge Gateway to Data Center Group VCD will attempt to validate the Static Routes.
This includes validating that the Next Hop IP Address and Scope (network) are valid.
If the Routed Organization VDC Network that the Static Route is scoped to is backed by multiple distributed port groups in multiple vCenter Servers, then this error can occur.

Resolution

This issue is under review with VMware Engineering. Subscribe to receive an email when the article is updated.

Workaround

To workaround this issue ensure that Network Pools in VCD are backed by NSX Transport Zones that only create distributed port groups in one vCenter Server to which VCD is connected.

Additional Information

For instances where the error gives a network name instead of a segment ID see the related article,  Error: "Unable to parse Uniform Resource Name (URN) ID: '<nsx_segment_name>'." when adding an Edge Gateway to Data Center Group.

Add an NSX Edge Gateway to a Data Center Group in the VMware Cloud Director Tenant Portal

Geneve Network Pools in Your VMware Cloud Director