Add VI/Cluster for VCF on VxRail during fails during Add ESXi Hosts to vSphere Distributed Switch

Products

• VMware Cloud Foundation

Issue/Introduction

To unblock VxRail customers from the above failure during add VI and add cluster workflows.

Symptoms:
Add VI/Cluster fails for VCF on VxRail in the "Add ESXi Hosts to vSphere Distributed Switch" action.

When

• VDS spec contains separate overlay VDS.
• vmnic to uplink mapping provided in the host spec
• vmnic to uplink mapping is not in sorted order.

Error Message:

vmnics in host hostname.example.local specified in request is not attached to DVS dvs-1 uplinks in lexicographic order {vmnic3=uplink3, vmnic1=uplink2, vmnic0=uplink1, vmnic5=uplink4}

VCF Domain Manager log: /var/log/vmware/vcf/domainmanager/domainmanager.log
 

2023-10-17T13:48:44.309+0000 ERROR [vcf_dm,6bf41c3b10e23a6f,cd4b] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-2] [I5FAT2] VSPHERE_VMNIC_NOT_ATTACHED_TO_PROPER_DVS_UPLINK vmnics in host hostname.example.local specified in request is not attached to DVS dvs-1 uplinks in lexicographic order {vmnic3=uplink3, vmnic1=uplink2, vmnic0=uplink1, vmnic5=uplink4}
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: vmnics in host hostname.example.local specified in request is not attached to DVS dvs-1 uplinks in lexicographic order {vmnic3=uplink3, vmnic1=uplink2, vmnic0=uplink1, vmnic5=uplink4}
at com.vmware.vcf.common.fsm.plugins.action.impl.AddHostsToDvsAction.validateVmnicsAreAttachedToDvs(AddHostsToDvsAction.java:566)
at com.vmware.vcf.common.fsm.plugins.action.impl.AddHostsToDvsAction.validateHostsDvs(AddHostsToDvsAction.java:540)
at com.vmware.vcf.common.fsm.plugins.action.impl.AddHostsToDvsAction.postValidate(AddHostsToDvsAction.java:434)
at com.vmware.vcf.common.fsm.plugins.action.impl.AddHostsToDvsAction.postValidate(AddHostsToDvsAction.java:52)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.lambda$static$1(FsmActionState.java:23)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:400)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:561)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
at jdk.internal.reflect.GeneratedMethodAccessor822.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
at org.springframework.cloud.sleuth.instrument.async.TraceRunnable.run(TraceRunnable.java:64)
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:833)
2023-10-17T13:48:44.363+0000 DEBUG [vcf_dm,6bf41c3b10e23a6f,cd4b] [c.v.e.s.o.c.ProcessingTaskSubscriber,dm-exec-2] Collected the following errors for task with name AddHostsToDvsAction and ID 7f000001-8b39-1003-818b-3d77aaf300f5: [ExecutionError [errorCode=null, errorResponse=LocalizableErrorResponse(messageBundle=com.vmware.vcf.common.vsphere.plugins.action.messages)]]

Environment

Vmware Cloud Foundation 5.1

Cause

It is due to a bug in VCF where it is not considering vmnic to uplink mapping mentioned in the spec.

Resolution

This is resolved in VCF 5.1.1

Workaround:
Please follow the below workaround:

1. From vCenter, reconfigure vmnic to uplink mapping in sorted order for the system VDS as mentioned in the error message in the VCF UI.

2. Retry the failed workflow.

3. Once the workflow is successful, reconfigure vmnic to uplink mapping for all the VDS as per input spec.