Bug 1322486

Summary: kubectl get cs always shows Unhealthy in OpenShift
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: NodeAssignee: Andy Goldstein <agoldste>
Status: CLOSED UPSTREAM QA Contact: Mike Fiedler <mifiedle>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: aos-bugs, jokerman, mifiedle, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-30 14:50:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Fiedler 2016-03-30 14:47:30 UTC 
Description of problem:

kubectl get cs always returns all component status as Unhealthy.  Cluster is otherwise operational and passes tests.

Version-Release number of selected component (if applicable):

OSE 3.2.0.8 (or a dev env with origin 1.1.5-20)

How reproducible: Always


Steps to Reproduce:
1.   Install OSE 3.2.0.8 (or a dev env with origin 1.1.5-20) 
2.   kubectl get cs


Actual results:

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-0               Unhealthy   Get http://172.18.10.11:4001/health: malformed HTTP response "\x15\x03\x01\x00\x02\x02"        

Expected results:

A healthy, working cluster should probably get a Healthy status.

Additional info:
Comment 1 Andy Goldstein 2016-03-30 14:50:27 UTC 
https://github.com/openshift/origin/issues/3667