Install button spinning for SDDC Enhanced Management Components deployment; VCF 9.1
search cancel

Install button spinning for SDDC Enhanced Management Components deployment; VCF 9.1

book

Article ID: 444904

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

  • The Install button remains in a spinning state during the deployment of SDDC Enhanced Management Components.



  • The VCF Operations UI and SDDC Manager UI displays the "Deploy VCF management components" task in a Failed state with an option to re-start the task. However, The task is failing again when re-attempting to re-start the task.



  • The subtask "Bootstrap VCF services Platform" reports the following error: Expected <Component-FQDN> to have at least one IP address.



  • Review of /var/log/vmware/vcf/domainmanager/domainmanager.log reveals errors similar to: 

    YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,6a##############################e7,c##3] [c.v.e.s.common.util.NetworkService,dm-exec-310] Error <Component-FQDN>: Name or service not known while resolving FQDN <Component-FQDN>
    YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,6a##############################e7,c##3] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-310] [2####9] PUBLIC_VSP_CLUSTER_BOOTSTRAP_FAILED Failed to bootstrap VCF services runtime
         com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to bootstrap VCF services runtime
         at com.vmware.vcf.vimanager.fsm.actions.BootstrapVspClusterAction.execute(BootstrapVspClusterAction.java:218)
         at com.vmware.vcf.vimanager.fsm.actions.BootstrapVspClusterAction.execute(BootstrapVspClusterAction.java:89)
         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:401)
         at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:515)
         at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:128)
              at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
         at java.base/java.lang.reflect.Method.invoke(Method.java:580)
         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:1144)
              at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
         at java.base/java.lang.Thread.run(Thread.java:1583)
    Caused by: java.lang.RuntimeException: Expected <Component-FQDN> to have at least one IP address.

Environment

VMware Cloud Foundation 9.1

Cause

VMware Cloud Foundation 9.1 strictly requires component Fully Qualified Domain Names (FQDNs) to be formatted in lowercase. Deployment stalls or becomes stuck in a spinning state if mixed-case FQDNs are specified during the initial configuration, resulting in DNS resolution failures during the bootstrap process.

Resolution

Broadcom is aware of this issue. Open a support case with Broadcom for further assistance with this issue. For instructions on how to create a case, refer to Creating and managing Broadcom cases

Additional Information

It is recommended to subscribe to this article to be updated on the fix status. For instructions on how to subscribe, refer to  Subscribe to a Broadcom knowledge article by article or product
 

Powered by Wolken Software