VCFA and VCFO Deployment Fails with Error: Failed to prepare data for management component deployment

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

• Deployment of VMware Cloud Foundation Automation (VCFA) and VMware Cloud Foundation Operations (VCFO) components on a dedicated overlay network fails with the following error:

  "Failed to prepare data for management component deployment"

• Reviewing domainmanager.log shows network connection failures and socket timeout exceptions:
  YYYY-MM-DDThh:mm:ss.173+0000 DEBUG [vcf_dm,6a15638614f6a3defb939a6b6a87a8a0,a3df] [c.v.e.s.common.util.NetworkService,dm-exec-2393] Cannot connect to port 80
YYYY-MM-DDThh:mm:ss.174+0000 DEBUG [vcf_dm,6a15638614f6a3defb939a6b6a87a8a0,a3df] [c.v.e.s.common.util.NetworkService,dm-exec-2393] Unable to open port 80 on <REDACTED_IP>
java.net.SocketTimeoutException: Connect timed out
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:546)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at com.vmware.evo.sddc.common.util.NetworkService.isPortOpen(NetworkService.java:905)
at com.vmware.evo.sddc.common.util.NetworkService.hostReachable(NetworkService.java:887)
at com.vmware.evo.sddc.common.util.NetworkService.hostReachable(NetworkService.java:873)
at com.vmware.evo.sddc.common.validation.primitive.NetworkValidator.validateIpUsage(NetworkValidator.java:246)
at com.vmware.evo.sddc.validation.util.NetworkConfigValidationUtil.lambda$validateIpUsage$0(NetworkConfigValidationUtil.java:50)
...
YYYY-MM-DDThh:mm:ss.225+0000 DEBUG [vcf_dm,6a15638614f6a3defb939a6b6a87a8a0,a3df] [c.v.e.s.common.util.NetworkService,dm-exec-2393] Cannot connect to port 8443
YYYY-MM-DDThh:mm:ss.225+0000 DEBUG [vcf_dm,6a15638614f6a3defb939a6b6a87a8a0,a3df] [c.v.e.s.common.util.NetworkService,dm-exec-2393] Unable to open port 8443 on <REDACTED_IP>
java.net.NoRouteToHostException: No route to host
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:549)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at com.vmware.evo.sddc.common.util.NetworkService.isPortOpen(NetworkService.java:905)
at com.vmware.evo.sddc.common.util.NetworkService.hostReachable(NetworkService.java:887)
at com.vmware.evo.sddc.common.util.NetworkService.hostReachable(NetworkService.java:873)
at com.vmware.evo.sddc.common.validation.primitive.NetworkValidator.validateIpUsage(NetworkValidator.java:246)

Environment

VMware Cloud Foundation 9.1

Cause

• The IP address configured in the .spec.values.ingress.platform.fqdn specification did not match the actual IP address that the provided platform FQDN resolved to via DNS.

• The Domain Manager requires strict forward and reverse DNS resolution matching the deployment specification to locate and communicate with the VSP API. The IP mismatch resulted in an Invalid SddcSpec state, preventing the vcf_dm service from verifying the Fleet LCM address.

Resolution

 

1. Verify the platform FQDN configured in the .spec.values.ingress.platform.fqdn specification.

2. Verify forward (A record) and reverse (PTR record) DNS resolution for the platform FQDN.

3. Update the DNS A and PTR records to ensure the platform FQDN strictly resolves to the IP address defined in the .spec.values.ingress.platform.fqdn specification.