OpenShift 3.11 install fails on AWS while waiting for control plane pods to become ready

Solution Unverified - Updated -

Issue

  • OpenShift 3.11 Installer is not using correct host/node name for control plane pods.
  • There is host/node name discrepancy while installing OpenShift 3.11 on AWS.
  • Why is OpenShift installer using private DNS name of the AWS instance when setting up the control plane pods?

Environment

  • OpenShift (OCP) 3.11
  • AWS Cloud

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