On OpenShift Container Platform atomic-openshift-master service fails with error "unable to confirm openshift-controller-manager lease exists: getsockopt: connection refused".

Solution Verified - Updated -

Issue

  • On 3master OCP set-up, only one master works and other two fails to start atomic-openshift-master-controllers, atomic-openshift-master-api, and etcd.service services.
Mar 14 19:31:05 master2 atomic-openshift-master-controllers[2854]: E0314 19:31:05.578445    2854 leaderelection.go:124] unable to confirm openshift-controller-manager lease exists: Get https://master2.example.com/api/v1/namespaces/kube-system/endpoints/openshift-controller-manager: dial tcp 192.x.x.x:443: getsockopt: connection refused
 atomic-openshift-master-controllers.service - Atomic OpenShift Master Controllers
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master-controllers.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-03-14 14:56:50 EDT; 4h 34min ago

Environment

  • OpenShift Container Platform 3.6

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