OpenShift nodes not ready with Vsphere cloud provider

Solution Verified - Updated -

Issue

  • OpenShift has compute nodes in NotReady state on VMWare Vsphere

  • Not ready nodes have more than one IP in their main interface (usually eth0)

    • A common reason for this is that not ready nodes hold egress IPs.
  • Not ready logs show the error messages depicted at "Diagnostic Steps" section of this solution.

Environment

  • OpenShift Container Platform 3.9 - 3.11 with Vsphere cloud provider enabled

  • VMWare vsphere, 6+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In