Cluster Creation Fails on Existing Workload Domain in SDDC Manager with Error: "Failed to validate host selection: Invalid Parameter: hostsOnly=False, skipHostSwitchValidation=true"
search cancel

Cluster Creation Fails on Existing Workload Domain in SDDC Manager with Error: "Failed to validate host selection: Invalid Parameter: hostsOnly=False, skipHostSwitchValidation=true"

book

Article ID: 405958

calendar_today

Updated On:

Products

VMware SDDC Manager VMware NSX

Issue/Introduction

  • Subtask failure in SDDC UI with Error- Failed to configure Vswitch to DVS vmknic migration. Failed ESXI Host(s) to skip: Host-1, Host-2, Host-3

 

  •  Cluster creation on an existing Workload Domain fails with the following error:

Error: Failed to validate host selection: Invalid Parameter: hostsOnly=False, skipHostSwitchValidation=true
(Provide the VDS configuration is applied to the hosts in the cluster.)


 

  • Domainmanager.log
    /var/log/vmware/vcf/domainmanager/domainmanager.log (Invalid Parameter)
    yyyy-mm-ddT06:##:33.563+1000 DEBUG [vcf_dm,3d0888#########,e257] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-12]  Processing localizable exception Invalid parameter: hostsOnly=false, skipHostSwitchValidation=true
    yyyy-mm-ddT06:##:33.563+1000 ERROR [vcf_dm,3cd0888#########,e257] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-12]  [3E##L2] VCF_ERRORS_GENERIC_INPUT_PARAM_ERROR Invalid parameter: hostsOnly=false, skipHostSwitchValidation=true
    com.vmware.vcf.clustermanager.error.ClusterControllerException: Invalid parameter: hostsOnly=false, skipHostSwitchValidation=true
            at com.vmware.vcf.clustermanager.controller.ClusterManagerIsController.validateSpec(ClusterManagerIsController.java:208)
            at jdk.internal.reflect.GeneratedMethodAccessor7127.invoke(Unknown Source)
            at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
            at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
            at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
            at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
            at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
            at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
            at java.base/java.lang.Thread.run(Thread.java:833)
    yyyy-mm-ddT06:##:33.564+1000 DEBUG [vcf_dm,3c8cf028d18a4727,5a09] [c.v.e.s.e.h.LocalizableRuntimeExceptionHandler,http-nio-127.0.0.1-7200-exec-12]  Handler Error Response: {"errorCode":"VCF_ERRORS_GENERIC_INPUT_PARAM_ERROR","arguments":["hostsOnly\u003dfalse, skipHostSwitchValidation\u003dtrue"],"message":"Invalid parameter: hostsOnly\u003dfalse, skipHostSwitchValidation\u003dtrue","referenceToken":"3E##L2"}
    yyyy-mm-ddT06:##:52.241+1000 INFO  [vcf_dm,dd08888##########,e257] [c.v.v.c.c.ClusterManagerIsController,http-nio-127.0.0.1-7200-exec-3]  Validating cluster spec {"domainId":"#######-f774-####-9938-##############","hostSpec":{"hostSystemSpec":[{"id":""#######-f774-####-9938-##############"},{"id":""#######-f774-####-9938-##############"}]}}
    yyyy-mm-ddT06:##:52.241+1000 DEBUG [vcf_dm,dd0888#########,e257] [c.v.e.s.c.s.a.l.LicenseServiceAdapterImpl,http-nio-127.0.0.1-7200-exec-3]  Checking subscription status for domain "#######-f774-####-9938-##############.
    yyyy-mm-ddT06:##:52.241+1000 DEBUG [vcf_dm,dd0888#########,e257] [c.v.e.s.c.s.a.l.LicenseServiceAdapterImpl,http-nio-127.0.0.1-7200-exec-3]  Get licensing info for domain "#######-f774-####-9938-##############
    yyyy-mm-ddT06:##:52.249+1000 DEBUG [vcf_dm,dd0888#########,e257] [c.v.e.s.c.s.a.l.LicenseServiceAdapterImpl,http-nio-127.0.0.1-7200-exec-3]  Obtained licensing info: {"isRegistered":false,"isSubscribed":false,"licensingMode":"PERPETUAL","resourceId":""#######-f774-####-9938-##############4","resourceType":"DOMAIN","subscriptionStatus":"UNSUBSCRIBED","entitlements":{"hasNsxEntitlement":false}}
    yyyy-mm-ddT06:##:52.249+1000 DEBUG [vcf_dm,dd0888#########,e257] [c.v.e.s.c.s.a.l.LicenseServiceAdapterImpl,http-nio-127.0.0.1-7200-exec-3]  {"isRegistered":false,"isSubscribed":false,"licensingMode":"PERPETUAL","resourceId":""#######-f774-####-9938-##############","resourceType":"DOMAIN","subscriptionStatus":"UNSUBSCRIBED","entitlements":{"hasNsxEntitlement":false}}
    yyyy-mm-ddT06:##:52.322+1000 DEBUG [vcf_dm,dd0888#########,e257] [c.v.v.c.s.v.ClusterValidationUtil,http-nio-127.0.0.1-7200-exec-3]  NSX Manager Optional.empty for domain #######-####-####-####-########

 

  • Domainmanager.log
    /var/log/vmware/vcf/domainmanager/domainmanager.log (Failed to configure Vswitch to DVS vmknic migration)
    yyyy-mm-ddT13:24:00.245+1000 ERROR [vcf_dm,b75d2cb8##########,8eb6] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-8]  [J####H] VSPHERE_MIGRATE_HOST_MGMT_VMKNICS_TO_DVS_FAILED_SKIP_FAILED_HOSTS Failed to configure Vswitch to DVS vmknic migration. Failed ESXi Host(s) to skip: [Host-1, Host-2, Host-3.]
    com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to configure Vswitch to DVS vmknic migration. Failed ESXi Host(s) to skip: [Host-1, Host-2, Host-3.]
            at com.vmware.vcf.common.fsm.plugins.action.impl.MigrateHostManagementVmknicsToDvsAction.skipFailedHosts(MigrateHostManagementVmknicsToDvsAction.java:190)
            at com.vmware.vcf.common.fsm.plugins.action.impl.MigrateHostManagementVmknicsToDvsAction.execute(MigrateHostManagementVmknicsToDvsAction.java:91)
            at com.vmware.vcf.common.fsm.plugins.action.impl.MigrateHostManagementVmknicsToDvsAction.execute(MigrateHostManagementVmknicsToDvsAction.java:27)
            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.GeneratedMethodAccessor7212.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)

Environment

  • VMware SDDC Manager

Cause

The SDDC UI is either sending an invalid payload or is unable to retrieve configuration data from NSX.

Misconfiguration in the VLAN IDs on the ESXi hosts, or the required VLANs are not allowed on the physical uplinks (vmnics).

 

Resolution

To unblock the workflow, please follow the steps below:

  1. On the "Add Cluster to" screen, navigate to the Switch Configuration page and select "Create Custom Switch Configuration".

     

  2. Click on “Copy from Preconfigured Profile” and choose an appropriate profile from the dropdown

  3. Edit the VDS name as needed and provide the appropriate VLAN ID
    Ensure that the specified VLAN IDs are allowed on the physical vmnics of the ESXi hosts.
    This is required for SDDC Manager to successfully migrate the vmknics from the Standard Switch to the Distributed Virtual Switch (DVS).
    Note: Engage physical network team to verify and update the VLAN trunk configuration on the physical switches.                                                                                                                                 
  4. Retry the failed workflow
Powered by Wolken Software