Installation of RHOCP3.11 fails with message "Control plane pods didn't come up and become ready"

Solution Verified - Updated -

Issue

  • A fresh installation of RHOCP v3.11 fails with error message Control plane pods didn't come up and become ready
TASK [openshift_control_plane : Report control plane errors] *****************************************************
task path: /home/ansible/openshift-ansible/roles/openshift_control_plane/tasks/main.yml:310
fatal: [master1.hostname.example.com]: FAILED! => {
    "changed": false,
    "msg": "Control plane pods didn't come up and become ready"
}

NO MORE HOSTS LEFT ***********************************************************************************************
        to retry, use: --limit @/home/ansible/openshift-ansible/playbooks/deploy_cluster.retry

PLAY RECAP *******************************************************************************************************
localhost                  : ok=11   changed=0    unreachable=0    failed=0
master1.hostname.example.com : ok=318  changed=119  unreachable=0    failed=1
infra1.hostname.example.com : ok=107  changed=33   unreachable=0    failed=0
infra2.hostname.example.com: ok=107  changed=33   unreachable=0    failed=0
compute1.hostname.example.com: ok=107  changed=33   unreachable=0    failed=0
compute2.hostname.example.com : ok=107  changed=33   unreachable=0    failed=0

INSTALLER STATUS *************************************************************************************************
Initialization              : Complete (0:00:32)
Health Check                : Complete (0:00:59)
Node Bootstrap Preparation  : Complete (0:05:39)
etcd Install                : Complete (0:00:51)
Master Install              : In Progress (0:22:10)
        This phase can be restarted by running: playbooks/openshift-master/config.yml

Failure summary:
  1. Hosts:        master1.hostname.example.com
     Play:           Configure masters
     Task:           Report control plane errors
     Message:  Control plane pods didn't come up and become ready
  • The connection to server was refused - did you specify the right host or port?
 "msg": {
        "cmd": "/bin/oc get pod master-etcd-master1.hostname.example.com -o json -n kube-system",
        "results": [
            {}
        ],
        "returncode": 1,
        "stderr": "The connection to the server master1.hostname.example.com:8443 was refused - did you specify the right host or port?\n",
        "stdout": ""
    }

Environment

  • Red Hat OpenShift Container Platform 3.11

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