Error: "OS Configuration Phase has failed." when deploying VCD with static routes configured

Products

• VMware Cloud Director

Issue/Introduction

• After the initial power on, the Cloud Director appliance management user interface (VAMI) shows an error when logging in on port 5480 via a browser:

  Configuration Failure

  OS Configuration Phase has failed.

  Please check the log at /opt/vmware/var/log/firstboot for more details on the failure before redeploying this appliance node.

• In vapp options, static routes are configured.
• This VCD Appliance VM can reach DNS servers only via the configured static routes, but cannot reach DNS servers via the default route.
• The /opt/vmware/var/log/firstboot log file on a Cloud Director Appliance shows these errors:

System hostname is: photon-machine
[ERROR] Hostname was not updated via dns reverse-lookup. Failing OS configuration phase.
[ERROR] Fix and verify DNS server info and other related networking settings, and redeploy this appliance again.

Environment

VMware Cloud Director 10.x

Cause

This behavior is because hostname is set by reverse-lookup before the static route is set. As a result, the hostname of this VM is set to the default "photon-machine".

Resolution

This is expected behavior during the installation of VMware Cloud Director appliances.

Please see the Host Name Resolution section in the Cloud Director documentation on Network Configuration Requirements for VMware Cloud Director for more details.

Workaround

In the initialization steps, DNS servers should be reached via the default route. After this, you can change DNS and route configurations of VMware Cloud Director appliances.

Additional Information

Network Configuration Requirements for VMware Cloud Director

 

Error: "Hostname was not updated via dns reverse-lookup. Failing OS configuration phase." configuration failure during initial power up of a Cloud Director Appliance