VCF 9.X deployment fails at "Deploy vCenter" stage with error 'com.vmware.vcIntegrity.lifecycle.host.communicationFailed'

Products

• VMware Cloud Foundation
• VMware SDDC Manager

Issue/Introduction

• During the Bring-up process of VMware Cloud Foundation (VCF) 9.0.x, the deployment fails during the Deploy vCenter stage. The VCF Installer reports a failure to connect to the ESXi host.
• /var/log/vmware/vcf/domainmanager/cli-installer-<date_and_time>/workflow_<#####>/vcsa-cli-installer.log on the VCF installer reports below error stack

  YYYY-MM-DD HH:MM:SS,746 - vCSACliInstallLogger - DEBUG - Task 'Running vSphere vLCM: Creating vSphere vLCM managed cluster.' execution failed because [Host seeding failed:(vmodl.MethodFault) {
     dynamicType = <unset>,
     dynamicProperty = (vmodl.DynamicProperty) [],
     msg = 'MethodFault.summary',
     faultCause = <unset>,
     faultMessage = (vmodl.LocalizableMessage) [
        (vmodl.LocalizableMessage) {
           dynamicType = <unset>,
           dynamicProperty = (vmodl.DynamicProperty) [],
           key = 'com.vmware.vcint.error_from_vlcm',
           arg = (vmodl.KeyAnyValue) [
              (vmodl.KeyAnyValue) {
                 dynamicType = <unset>,
                 dynamicProperty = (vmodl.DynamicProperty) [],
                 key = 'vlcm_error',
                 value = "Error:\n   com.vmware.vapi.std.errors.internal_server_error\nMessages:\n   com.vmware.vcIntegrity.lifecycle.host.communicationFailed<Host esx.example.com is not reachable. Check host's connectivity and health in vCenter and retry.>\n"
              }
           ],
           message = "An internal error occurred: 'Error:\n   com.vmware.vapi.std.errors.internal_server_error\nMessages:\n   com.vmware.vcIntegrity.lifecycle.host.communicationFailed<Host esx.example.com is not reachable. Check host's connectivity and health in vCenter and retry.>\n'"

Environment

VCF 9.X

Cause

• Issue is caused by communication issue between the vCenter and ESXi hosts. This was caused by an incorrect DNS configuration on the vCenter, which resulted in the vCenter being deployed on the incorrect subnet.

Resolution

• Check if the vCenter VM is getting deployed on the correct subnet from the VM console by directly connecting to the ESX host.
• If the vCenter VM is getting deployed on the wrong subnet, then correct the DNS issue by editing the deployment JSON file from the VCF installer UI.
• Re-try the deployment.