SDDC Manager 9.1 UI fails to load with "VMware Cloud Foundation is initializing" due to DNS resolution errors
search cancel

SDDC Manager 9.1 UI fails to load with "VMware Cloud Foundation is initializing" due to DNS resolution errors

book

Article ID: 444111

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

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.

  • SSH access to the SDDC Manager appliance reveals errors in /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.local
    com.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.

  • Running nmctl shows network configuration, but no DNS servers.

Environment

VMware Cloud Foundation (VCF) 9.1

SDDC Manager 9.1

Cause

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

Resolution

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:

  1. SSH into the SDDC Manager VM as the vcf user and switch to root.
  2. Configure the DNS servers using nmctl (ensure no spaces follow the commas between IPs):
    bash
     
    /usr/bin/nmctl set-dns dev eth0 dns <DNS-IP-1>,<DNS-IP-2>
  3. Verify that /etc/resolv.conf now contains the correct nameserver entries.
  4. Verify that nmctl now displays the DNS servers.
  5. Use nslookup to confirm the Management vCenter FQDN resolves correctly.
  6. Restart the SDDC Manager services or the VM:
    bash
     
    systemctl restart vcf-commonsvcs
  7. Verify the SDDC Manager UI loads successfully.

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 Contact Broadcom Support.

Additional Information

Collecting diagnostic information from VMware SDDC Manager

Configure/Update DNS Server IP Address in SDDC Manager or the VCF Installer through Command Line