VCF 9.0 WLD deployment fails on stage, "Tag VLAN IDs on Distributed Port Groups"

Products

• VCF Operations
• VMware Cloud Foundation

Issue/Introduction

The WLD domain is using the same portgroup names as the management domain.

/var/log/vmware/vcf/domainmanager/domainmanager.log
======================================================================================
DistributedVirtualPortgroup with moid null from vcenter
[YYYY-MM-DDTHH:MM:SS] DEBUG [vcf_dm,686566e269241fef19ca0064eef27cf0,8bac] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-1] Retrieved MoRef: {"_
type":"DistributedVirtualPortgroup"}
[YYYY-MM-DDTHH:MM:SS] ERROR [vcf_dm,686566e269241fef19ca0064eef27cf0,8bac] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-1] [BC653A] TAG_VLAN_ON_
PORTGROUP_EXECUTE_FAILED Error while tagging vlan ID null on DV port group 3901
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Error while tagging vlan ID null on DV port group 3901
        at com.vmware.vcf.common.fsm.plugins.action.impl.TagVlanIdsOnPortGroupsAction.execute(TagVlanIdsOnPortGroupsAction.java:55)
        at com.vmware.vcf.common.fsm.plugins.action.impl.TagVlanIdsOnPortGroupsAction.execute(TagVlanIdsOnPortGroupsAction.java:33)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:66)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:161)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:147)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:403)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:517)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:128)
        at jdk.internal.reflect.GeneratedMethodAccessor855.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)
        at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
        at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
        at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:63)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
       at java.base/java.lang.Thread.run(Thread.java:840)

Environment

VMware Cloud Foundation 9.0 

Cause

This is a known limitation with SDDC Manager and will be fixed in a future release of VCF.

Resolution

1. Delete the failed domain attempt directly from the SDDC Manager UI
   
   
2. Reimage the first ESXi host from the failed WLD attempt. (Delete the vSAN Datastore configuration)
   
   
3. Deploy the WLD domain again from VCF-Operations with unique portgroup names.