OpenShift 4 installation fails because of Windows DHCP Server

Solution Verified - Updated -

Issue

  • Hosts obtain the IP Address from DHCP correctly.

  • Hosts are not able to obtain the hostname from DHCP. The logs show:

    Nov 01 08:25:11 localhost.localdomain mco-hostname[1745]: waiting for non-localhost hostname to be assigned
Nov 01 08:25:11 localhost.localdomain systemd[1]: Starting Wait for a non-localhost hostname...
Nov 01 08:30:11 localhost.localdomain systemd[1]: node-valid-hostname.service: start operation timed out. Terminating.
Nov 01 08:30:11 localhost.localdomain systemd[1]: node-valid-hostname.service: Main process exited, code=killed, status=15/TERM
Nov 01 08:30:11 localhost.localdomain systemd[1]: node-valid-hostname.service: Failed with result 'timeout'.
Nov 01 08:30:11 localhost.localdomain systemd[1]: Failed to start Wait for a non-localhost hostname.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • Experienced with 4.12.
  • Nutanix Cloud Platform.

Please note that the root cause is transversal to this verified environment. This issue may be observed in other versions of RHOCP or other platforms.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content