VCF 9.0 Deployment Fails Due to DVPortGroup Naming with Forward Slash

Products

• VCF Operations

Issue/Introduction

VMware Cloud Foundation (VCF) 9.0.x deployment fails to detect the specified network when the DVPortGroup name contains a forward slash (/). NTP ping errors were also observed due to security restrictions, but the main blocker was network detection.

 

/var/log/vrlcm/vmware_vrlcm.log:

YYYY-MM-DDTHH:MM:SS INFO vrlcm[1252] [pool-3-thread-87] [c.v.v.l.c.v.c.FetchContentLibrariesTask] – Length of vCenter inventory: 5241
YYYY-MM-DDTHH:MM:SS INFO vrlcm[1252] [pool-3-thread-87] [c.v.v.l.p.a.s.Task] – Injecting Edge :: OnSuccessfullyFetchingContentLibraryInfo
YYYY-MM-DDTHH:MM:SS INFO vrlcm[1252] [pool-3-thread-87] [c.v.v.l.p.a.s.Task] – ========================================
{
"networks" : [
{ "network" : "###-dvs-DVUplinks-xx", "isManaged" : null },
{ "network" : "###-mgmt-###-10.###.##.0/24", "isManaged" : null },
{ "network" : "###-vapp-###-10.###.##.0/24", "isManaged" : null },
{ "network" : "###-vmo-###-10.###.##.0/24", "isManaged" : null }
],
YYYY-MM-DDTHH:MM:SS INFO vrlcm[1252] [http-nio-8080-exec-8] [c.v.v.l.r.c.RequestController] – Retry error cause data : 
[ {
"messageId" : "LCMVSPHERECONFIG1000041",
"message" : "Invalid network details. Ensure the provided network is present in vCenter or retry giving the right network details.",
"eventId" : "########-####-####-####-############",
"retry" : true,
"exceptionMessage" : "Invalid network providedfor the request.",
"exceptionStackTrace" : "com.vmware.vrealize.lcm.common.exception.userinput.InvalidNetworkDetails: Exception occurred while validating inputs for product : vrops. Unable to find networks : [\"###-vapp-####-10.###.##.0/24\"] for the given clusterMO ::Stub: moRef = (ManagedObjectReference: type = ClusterComputeResource, value = domain-c##, serverGuid = null), binding = https://<VC_hostname.example.com>/sdk/vimService\n\tat com.vmware.vrealize.lcm.drivers.vsphere65.deploy.impl.BaseOvfDeploy.getDeployOptionsMOR(BaseOvfDeploy.java:1298)\n\tat com.vmware.vrealize.lcm.plugin.core.vsphere.tasks.ValidateDeployInputsTask.execute(ValidateDeployInputsTask.java:276)\n\tat com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158)\n\tat com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n",
"localizedMessageId" : "VSPHERE_INVALIDNETWORK_ERROR",
"parameters" : null,
"properties" :
{ "hostName" : "<vcfops.example.com>", "netmask" : "###.###.###.0", "ip" : "10.###.##.##", "domain" : "<example.com>", "vcUsername" : <[email protected]>, "dns" : "10.###.###.1,10.###.###.2", "vCenterHost" : "<VC_hostname.example.com>", "vcPassword" : "########", "gateway" : "10.###.##.1", "searchpath" : "<example.com>", "network" : "###-vapp-####-10.###.##.0/24" }
} ]

 

Environment

VMware Cloud Foundation 9.0.x

Cause

vCenter server encodes forward slashes (/) in DVPortGroup names as %2f. VCF Lifecycle Manager looks for the unencoded name, causing a mismatch and failure to locate the network.

Resolution

This issue is known to us.

 

Workaround:

Required to use underscores (_) instead of slashes in DVPortGroup names.

Example:
Use network - ##.##.##.x_xx instead of network - ##.##.##.x/xx