Deployment of the Workload Domain from SDDC Manager doesn't work due to the failure of removing Virtual Switch vSwitch0 on ESXi Host
search cancel

Deployment of the Workload Domain from SDDC Manager doesn't work due to the failure of removing Virtual Switch vSwitch0 on ESXi Host

book

Article ID: 411478

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Deployment of the Workload Domain failed, and domainmanager.log on SDDC Manager shows the error code VALIDATE_NETWORK_CONNECTIVITY_FAILED_TO_CLEAN_UP_HOSTS_FROM_PREVIOUS_RUNS.

YYYY-MM-DDT02:33:31.459+0000 WARN  [vcf_dm,68cb6f5507eae7947008b1f7ff7db04c,8ece] [c.v.e.s.v.v.SinglePortgroupValidator,dm-exec-3]  Clean up of ESXi Host FO-IKF-SWSV-A001.ocx-compute-stg.internal failed
com.vmware.evo.sddc.common.hostservices.error.HostNetworkingException: Failed to remove Virtual Switch vSwitch0 on ESXi Host ####
...

Caused by: com.vmware.vim.binding.vim.fault.ResourceInUse: The resource 'vSwitch0' is in use.




YYYY-MM-DDT02:33:31.722+0000 ERROR [vcf_dm,68cb6f5507eae7947008b1f7ff7db04c,8ece] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-3]  [33HLD2] VALIDATE_NETWORK_CONNECTIVITY_FAILED_TO_CLEAN_UP_HOSTS_FROM_PREVIOUS_RUNS Failed to clean up ESXi Host(s) ####, ####, ####, #### from previous run(s) of the vMotion Network Connectivity Validation
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to clean up ESXi Host(s) ####, ####, ####, #### from previous run(s) of the vMotion Network Connectivity Validation
        at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateEsxiHostNetworkConnectivityAction.validateHostsConnectivity(ValidateEsxiHostNetworkConnectivityAction.java:181)
        at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateEsxiHostNetworkConnectivityAction.execute(ValidateEsxiHostNetworkConnectivityAction.java:146)
        at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateEsxiHostNetworkConnectivityAction.execute(ValidateEsxiHostNetworkConnectivityAction.java:50)
        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:520)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
        at jdk.internal.reflect.GeneratedMethodAccessor300.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:59)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

 

On the other hand, ESXi hostd.log shows the following messages.

YYYY-MM-DDT08:14:26.003Z In(166) Hostd[2099076]: [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 135 : Lost network connectivity on virtual switch "vSwitch0". Physical NIC vmnicX is down. Affected portgroups:"Management Network".
...
YYYY-MM-DDT10:37:43.584Z In(166) Hostd[2099101]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Cannot remove switch [vSwitch0]: 1 virtual NICs attached to portgroup Management Network
YYYY-MM-DDT10:37:43.584Z In(166) Hostd[2099101]: [Originator@6876 sub=AdapterServer opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] AdapterServer caught exception; <<5210a1eb-97ac-9c3c-2e1b-b31e4bf0f268, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 42559'>>, networkSystem, vim.host.NetworkSystem.removeVirtualSwitch, <vim.version.v7_0, internal, 7.0.0.0>, [N11HostdCommon18VmomiAdapterServer19ActivationResponderE:0x000000a135c04128]>, N3Vim5Fault13ResourceInUse9ExceptionE(Fault cause: vim.fault.ResourceInUse
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: --> )
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: --> [context]zKq7AVICAgAAAL9+cgEMaG9zdGQAAOPJR2xpYnZtYWNvcmUuc28AASR5XWhvc3RkAAERh3QBr9eGATaXfIKbdlkBbGlidmltLXR5cGVzLnNvAAG1lWIAHtssAOD/LAA7UFIDUngAbGlicHRocmVhZC5zby4wAAQ/Ug9saWJjLnNvLjYA[/context]
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099101]: [Originator@6876 sub=Vimsvc.TaskManager opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Task Completed : haTask-ha-host-vim.host.NetworkSystem.removeVirtualSwitch-187 Status error
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099101]: [Originator@6876 sub=Solo.Vmomi opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Activation finished; <<5210a1eb-97ac-9c3c-2e1b-b31e4bf0f268, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 42559'>>, networkSystem, vim.host.NetworkSystem.removeVirtualSwitch, <vim.version.v7_0, internal, 7.0.0.0>, [N11HostdCommon18VmomiAdapterServer19ActivationResponderE:0x000000a135c04128]>
YYYY-MM-DDT10:37:43.588Z Db(167) Hostd[2099101]: [Originator@6876 sub=Solo.Vmomi opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Arg vswitchName:
YYYY-MM-DDT10:37:43.588Z Db(167) Hostd[2099062]: --> "vSwitch0"
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099101]: [Originator@6876 sub=Solo.Vmomi opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Throw vim.fault.ResourceInUse
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099101]: [Originator@6876 sub=Solo.Vmomi opID=2ad2bfd5 sid=5210a1eb user=svc-vcf-####] Result:
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: --> (vim.fault.ResourceInUse) {
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: -->    type = "vim.host.VirtualSwitch",
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: -->    name = "vSwitch0",
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: -->    msg = "",
YYYY-MM-DDT10:37:43.588Z In(166) Hostd[2099062]: --> }

 

 

Environment

SDDC Manager 5.2.1

Cause

The expected configuration is for vSwitch0 to have one vmnic. If vSwitch0 has two or more vmnics, SDDC Manager can not complete the deployment task.

 

Resolution

Before commissioning ESXi hosts to SDDC Manager, verify the vmnic configuration.

Powered by Wolken Software