Description of problem
When I disable scheduling on a node, is easy to miss this information on a node
list and node page in OCP console.
Version-Release number of selected component
Steps to Reproduce
1. Install OCP cluster
2. Select one node and disable scheduling on it: oc adm cordon <node-name>
3. Open OCP Console, and go to list of Nodes (Admin -> Compute -> Nodes),
look for the node you cordoned
4. Open Node page of the cordoned node and look for Status of the node
Status of the node is reported as: Ready and Scheduling disabled, but the
information about scheduling is easy to miss.
Step #3: text "Scheduling disabled" is listed in status of the node, but
is downplayed via gray font color. See screenshot #1.
Step #4: text "Scheduling disabled" is listed, but it's almost invisible: font
color is grey and it's also faded into backgroud. See screenshot #2.
Scheduling status is communicated with same urgency as any other node status.
Font of scheduling status should be the same for all it's text (both "Ready"
and "Scheduling disabled" are readable and visible in the same way).
Created attachment 1713649 [details]
screenshot #1: list of nodes, with one cordoned node
Created attachment 1713650 [details]
screenshot #2: page of the cordoned node
This is also an accessibility issue as the text does not have enough contrast.
Was not able to get to this bug this sprint as we were prioritizing 4.6 blockers.
Fix is not contained in payload: 4.7.0-0.nightly-2020-10-27-051128, wait for new build.
Created attachment 1726164 [details]
Nodes list Ready but scheduling disabled
Created attachment 1726165 [details]
Node page Ready but scheduling disabled
Now a Ready, Scheduling disabled node will be shown in yellow warning icon(exclamation icon), this should not easy to miss
Verified on 4.7.0-0.ci-2020-11-03-041130
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.