Wrong hostname causes "Node notReady" state of the nodes on UPI bare metal OCP cluster

Solution Verified - Updated -

Issue

  • The hostname of the OCP cluter node is set dynamically by the NetworkManager, using DNS lookup
  • Sometimes the NetworkManager is using wrong IP Address (eg. the Egress IP Address) for the query and the DNS server returns wrong hostname
  • Setting the wrong hostname leads to certificate problems and Node notReady state of the cluster node

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.8+
  • UPI on bare metal with customized ISO for every node
  • Static Network configuration and IP Addresses on all nodes

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