VMware Cloud Foundation on VxRail 3.7.x bringup fails while getting Portgroup details from the vCenter Server

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:
The below messages are seen in /var/log/vmware/vcf/bringup/vcf-bringup-debug.log

2019-06-27T12:38:24.472+0000 [bringup-app-ems,[3f16407a6bcfd003,281d]] ERROR [c.v.e.s.b.a.t.v.MigrateVmsToMgmtPortGroupBringupAdapter,pool-2-thread-10] Failed to get vCenter server network details from vCenter

2019-06-27T12:38:24.472+0000 [bringup-app-ems,[3f16407a6bcfd003,281d]] ERROR [c.v.e.s.o.c.ProcessingTaskSubscriber,pool-2-thread-10] method invocation target not found

java.lang.reflect.InvocationTargetException: null

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.getParams(ProcessingTaskSubscriber.java:266)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:299)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:431)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:96)

at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:55)

at reactor.bus.EventBus$3.accept(EventBus.java:317)

at reactor.bus.EventBus$3.accept(EventBus.java:310)

at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72)

at reactor.bus.EventBus.accept(EventBus.java:591)

at reactor.bus.EventBus.accept(EventBus.java:63)

at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160)

at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74)

at org.springframework.cloud.sleuth.instrument.async.LocalComponentTraceRunnable.run(LocalComponentTraceRunnable.java:53)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: java.lang.IllegalStateException: Failed to get vCenter server network details from vCenter

at com.vmware.evo.sddc.bringup.adapters.toplugin.vxrail.MigrateVmsToMgmtPortGroupBringupAdapter.getVcenterNetworkPortGroupName(MigrateVmsToMgmtPortGroupBringupAdapter.java:131)

at com.vmware.evo.sddc.bringup.adapters.toplugin.vxrail.MigrateVmsToMgmtPortGroupBringupAdapter.toPlugin(MigrateVmsToMgmtPortGroupBringupAdapter.java:87)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Foundation on VxRail 3.7.x

Cause

After the VxRail first run the portgroup names created on the management ESXI hosts cannot be changed as automated bringup will look for the pre-defined port group names configured during VxRail first run.

Resolution

This is a expected behavior.

Workaround:
To resolve the bringup failure, the portgroup names will need to be reverted to their original names and the Cloud Builder will need to redeployed and the process will need to be started from the beginning.

To change the portgroup names, please see the official documentation here.

To redeploy the Cloud Builder VM, please see the official deployment documentation here. Once the Cloud Builder VM is deployed successfully please continue the bringup process.