Workload domain creation fails on the Deploy vCenter Server Appliance task and the retry option is not successful

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• An attempt to create a workload domain fails at the task Deploy vCenter Server Appliance.
• In the vSphere client for the vCenter Server in the management workload domain, you see that the Power On virtual machine task for the new vCenter Server has failed with a message stating: Insufficient resources to satisfy  configured failover level for vSphere HA.
• The vCenter Server Appliance deployed during the attempt to create a workload domain is still present in the vCenter Server inventory in a powered-off state
• After increasing the compute capacity in the management workload domain to accommodate the new vCenter Server VM, attempt to restart the failed workflow fails.
• You see messages similar to the following in the /var/log/vmware/vcf/domainmanager/domainmanager.log file on the SDDC Manager VM:

2018-10-30 07:50:23.497 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] ERROR [   c.v.e.s.c.client.vmware.vsphere.VsphereClient]   Failed to connect to https://10.0.0.150/sdk
com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

2018-10-30 07:50:23.499 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] WARN  [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase]   Shutting down the connection monitor.

2018-10-30 07:50:23.499 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] INFO  [   c.v.e.s.c.client.vmware.vsphere.VcManagerBase]   Failed java.net.NoRouteToHostException: No route to host (Host unreachable)
2018-10-30 07:50:23.499 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] DEBUG [   c.v.e.s.c.client.vmware.vsphere.VcManagerBase]   VCenter login failed for 10.0.0.150, will retry in 20 seconds!
2018-10-30 07:50:23.499 [vcf_dm,,] [monitor-59] WARN  [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase]   Interrupted, no more connection pool cleanups will be performed.
2018-10-30 07:50:46.500 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] ERROR [   c.v.e.s.c.client.vmware.vsphere.VsphereClient]   Failed to connect to https://10.0.0.150/sdk
com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

2018-10-30 07:51:29.530 [vcf_dm,d2fd2fc196636f6b,93a0ba9f1e3486b0] [1-thread-8] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory]   [VHH9GQ] DEPLOY_VC_VALIDATION_FAILED Validation of vCenter VM VC-VI failed.

com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Validation of vCenter VM VC-VI failed.

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

Environment

VMware Cloud Foundation 3.0.x
VMware Cloud Foundation 3.5.x

Resolution

This is a known issue affecting VMware Cloud Foundation 3.x. There is currently no resolution.

Workaround:
To workaround this issue, delete the new vCenter Server VM and then retry the failed workflow.

Additional Information

To be alerted when this article is updated, click the subscribe button [cid:[email protected]] . For more information on KB subscription features, see the Knowledge Base Article FAQs: How to Subscribe to VMware Knowledge Base Articles (76417).