The VCF 9.1 Installer showed that the SDDC Manager deployment completed successfully, but the SDDC Manager UI failed to load with a VMware Cloud Foundation is initializing message.
/var/log/vmware/vcf/commonsvcs/vcf-commonsvcs.log: ERROR [common,0000000000000000,0000] [c.v.e.s.c.c.v.vsphere.VsphereClient,cs-exec-10] Failed to connect to https://<vcenter fqdn>:443/sdk as <svc-account>@vsphere.localcom.vmware.vim.vmomi.client.exception.ConnectionException: https://<vcenter>:443/sdk invocation failed with "java.net.UnknownHostException: <vcenter fqdn>: Temporary failure in name resolution"/etc/resolv.conf is missing nameserver entries.nmctl shows network configuration, but no DNS servers.VMware Cloud Foundation (VCF) 9.1
SDDC Manager 9.1
A space character included in the DNS server list during OVF deployment causes the nmctl parser to fail. This results in the DNS configuration not being persisted to the system after the initial boot.
Journal logs show the following parsing error:
cap_init[1093]: ++ /usr/bin/nmctl set-dns dev eth0 dns #.#.#.#, #.#.#.#
cap_init[1093]: ** (process:1655): WARNING **: 12:11:56.682: Failed to parse '#.#.#.#': Invalid argument
Fixed in release 9.1.1 and higher. See for steps to download this release.
For environments currently on 9.1.0, follow these steps to manually remediate the DNS configuration:
vcf user and switch to root.nmctl (ensure no spaces follow the commas between IPs):/etc/resolv.conf now contains the correct nameserver entries.nmctl now displays the DNS servers.nslookup to confirm the Management vCenter FQDN resolves correctly.Note: If the UI remains stuck, verify if there is a case-sensitivity mismatch in the SDDC Managerknown_hosts files as detailed in Article 442142.
If the issue persists, see .