"Internal Server Error" when trying to create a direct network in Cloud Director while NSX-T Segment Profile Templates are in use.

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Following network creation task failure, you see the following stacktrace in the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log:

networking-web-activity-pool-227391 | NsxTOrgVdcNetwork | Exception occurred while creating orgVdc network xxxxxx in vdc | requestId=xxxxxxxxxxxxxxxxxxxxxx,request=POST https://vcd.example.com/cloudapi/1.0.0/orgVdcNetworks,requestTime=1698920178275,remoteAddress=xx.xx.xxx.xx:xxxx,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/json;version 38.0.0-alpha;multisite xxxxxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxxx vcd=xxxxxxxxxxxxxxxxxxxxxx,task=xxxxxxxxxxxxxxxxxxxxxx activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:xxxxxxxxxxxxxxxxxxxxxx) activity=(com.vmware.vcloud.networking.services.handlerproxy.activity.networks.OrgVdcNetworkActivity,urn:uuid:xxxxxxxxxxxxxxxxxxxxxx)
java.lang.NullPointerException 
at com.vmware.vcloud.networking.model.nsxtresource.segment.segmentprofile.NsxTSegmentProfileMappings.setIpDiscoveryProfilePath(NsxTSegmentProfileMappings.java:455) at com.vmware.vcloud.networking.model.nsxtresource.segment.segmentprofile.NsxTSegmentProfileMappings.updateIpMacDiscoveryBinding(NsxTSegmentProfileMappings.java:382) at com.vmware.vcloud.networking.model.nsxtresource.segment.segmentprofile.NsxTSegmentProfileMappings.updateSegment(NsxTSegmentProfileMappings.java:338) at com.vmware.vcloud.networking.model.network.TenantNetwork.configureNsxTSegmentProfileTemplate(TenantNetwork.java:663) at com.vmware.vcloud.networking.model.network.NsxTOrgVdcNetwork.createAndDeploy(NsxTOrgVdcNetwork.java:139) at com.vmware.vcloud.networking.services.handlerproxy.activity.networks.OrgVdcNetworkActivity.createOrgVdcNetwork(OrgVdcNetworkActivity.java:33)

Environment

VMware Cloud Director 10.x

Cause

This is a known issue in the Cloud director 10.4.2 version. 

The issue happens because Cloud Director is incorrectly trying to set Segment Profiles for the Network Backing which is a VLAN Backed DV (Distributed) Port Group, however, it is not supposed to set Segment Profiles for any Direct network, be it VLAN backed DV Port group or NSX-T Segment backed.

Resolution

This issue is resolved in the Cloud Director 10.4.3 and 10.5.1 versions.

Workaround:

To work around this issue if you do not want to upgrade, temporarily mark the Global Defaults setting as 'Not set':

1. Open the Cloud Director Provider Portal.
2. Go into the Infrastructure Resources pane.
3. Under NSX-T, access the Segment Profile Templates.
4. Go into the Global Defaults section and press Edit.
5. Mark the VDC networks and vApp Networks settings as 'Not Set'.

Reference: Set a Global Default Segment Profiles Template