Red Hat Bugzilla – Bug 1268988
oc get componentstatus shows an Unhealthy status
Last modified: 2017-08-25 12:24:26 EDT
Description of problem:
The oc get cs command should accurately display the component status however it fails to complete the check which results in an Unhealthy status being reported.
Version-Release number of selected component (if applicable):
OpenShift Enterprise version 3.0.2
Steps to Reproduce:
1. Setup environment according to directions
2. run `oc get cs`
See that the status of various parts of the system; scheduler, controller-manager, and etcd are in an Unhealthy status.
If system was Just set up, they should all be in a healthy status.
Identified on github as well, https://github.com/openshift/origin/issues/3667
From reading the upstream bug it sounds like we'll have to fix this in Kubernetes.
This will not make 3.1, it requires significant upstream changes. Summary is on https://github.com/openshift/origin/issues/3667
*** Bug 1288871 has been marked as a duplicate of this bug. ***
I understand it is no small endeavor, however, is this something that could make a future release? 3.1 is already out but potentially 3.2 or further?
Yes, I am marking this upcoming release again. Most likely this would be a candidate for 3.4.
The kubernetes componentstatuses API have hard-coded assumptions about cluster topology that are incorrect and insecure (it assumes components are running on localhost, assumes they are running insecurely, and assumes they are using hardcoded ports).
It is not supported or expected to work in Openshift.