master controllers starts producing the error "etcd cluster is unavailable or misconfigured"

Solution In Progress - Updated -

Issue

  • atomic-openshift-master-controllers service starts producing the error:
Jan 30 14:02:04 knakayam-ose33-master1.example.com atomic-openshift-master-controllers[2627]: E0130 14:02:04.514779    2627 nodecontroller.go:574] Unable to mark all pods NotReady on node knakayam-ose33-master2.example.com: client: etcd cluster is unavailable or misconfigured; client: etcd cluster is unavailable or misconfigured
...
Jan 30 14:13:46 knakayam-ose33-master1.example.com atomic-openshift-master-controllers[8138]: E0130 14:13:46.651637    8138 leaderlease.go:69] unable to check lease openshift.io/leases/controllers: 501: All the given peers are not reachable (failed to propose on members [https://knakayam-ose33-master2.example.com:2379 https://knakayam-ose33-master3.example.com:2379 https://knakayam-ose33-master1.example.com:2379] twice [last error: Unexpected HTTP status code]) [0]
  • oc get node doesn't report the Node status correctly after this error happened.

Environment

  • OpenShift Container Platform
    • 3.x

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.