oc get componentstatus - Unhealthy

Solution In Progress - Updated -

Issue

The OpenShift Enterprise environment is operation properly, however the status command shows Unhealthy states for components:
Openshift Enterprise 3.1

# oc get componentstatus
NAME                 STATUS      MESSAGE   ERROR
controller-manager   Unhealthy             Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252: connection refused
scheduler            Unhealthy             Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connection refused
etcd-0               Unhealthy             Get http://master.demo.lan:4001/health: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

Openshift Container Platform 3.2 and later

[root@master1 ~]# oc get componentstatus
NAME                 STATUS      MESSAGE                                                                                           ERROR
scheduler            Unhealthy   Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: getsockopt: connection refused      
controller-manager   Unhealthy   Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252: getsockopt: connection refused      
etcd-2               Unhealthy   Get https://<etcd_server3>:2379/health: remote error: tls: bad certificate   
etcd-0               Unhealthy   Get https://<etcd_server1>:2379/health: remote error: tls: bad certificate   
etcd-1               Unhealthy   Get https://<etcd_server2>:2379/health: remote error: tls: bad certificate   

is this expected and how can it be fixed?

Environment

  • OpenShift Enterprise 3.1 and later

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.