Bug 1322486 - kubectl get cs always shows Unhealthy in OpenShift
Summary: kubectl get cs always shows Unhealthy in OpenShift
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Andy Goldstein
QA Contact: Mike Fiedler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 14:47 UTC by Mike Fiedler
Modified: 2016-03-30 14:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-30 14:50:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.