Bug 1748405

Summary:	Unschedulable status is not reflected in the UI
Product:	OpenShift Container Platform	Reporter:	Udi Kalifon <ukalifon>
Component:	Management Console	Assignee:	Samuel Padgett <spadgett>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aos-bugs, jokerman, yanpzhan, yapei
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, the web console did not show when a node was unscheduleable in the node list. This was inconsistent with the CLI. The console now shows when a node is unscheduleable from the node list and node details pages.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:39:51 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:
Embargoed:

Description Udi Kalifon 2019-09-03 14:08:21 UTC

Description of problem:
From the GUI, browse to the Nodes page and mark one of the nodes as unschedulable (it's the first command in the kebab menu). Click on confirm when the dialog pops up. From the CLI, you can see that the node status is now "Ready,SchedulingDisabled":

$ oc get nodes
NAME STATUS ROLES AGE VERSION
rhhi-node-master-2 Ready,SchedulingDisabled master,worker 22h v1.14.0+5ccbd432f

However, from the GUI you see no change (even after pressing F5). Only 1 status is displayed: "Ready". It seems like the GUI doesn't support multiple items in the status.


How reproducible:
100%


Steps to Reproduce:
1. Mark a node as unschedulable


Actual results:
No change is seen in the GUI


Expected results:
The status in the GUI should be the same as in the CLI


Additional info:
The status in the CLI shows 2 statuses: "Ready,SchedulingDisabled".
Jira bug: https://jira.coreos.com/browse/KNIDEPLOY-921

Comment 1 Jiri Tomasek 2019-09-04 13:50:43 UTC

This seems like a feature request to me. The node being marked unschedulable is currently not reflected in it's status in UI. Also this belongs to the core console component. So I am moving at and marking as 4.3 target.

Comment 2 Samuel Padgett 2019-09-04 15:32:28 UTC

This is currently working as intended, but we should align with the CLI.

Comment 4 Yanping Zhang 2019-09-05 08:27:53 UTC

Fix is not contained in payload 4.2.0-0.nightly-2019-09-04-215255. Waiting for new payload.

Comment 6 Yanping Zhang 2019-09-09 02:02:09 UTC

Payload: 4.2.0-0.nightly-2019-09-08-180038 
Console commit: https://github.com/openshift/console/commit/d26fdd4766eb56471e29cde24c54cd27f062cbbf
Checked on ocp 4.2 env with above version, when mark node as unschedulable from console, will show "Scheduling Disabled" in gray color for the node status.
The bug has been fixed, so move it to Verified.

Comment 7 errata-xmlrpc 2019-10-16 06:39:51 UTC

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922

Comment 8 Samuel Padgett 2019-10-28 13:55:56 UTC

*** Bug 1608742 has been marked as a duplicate of this bug. ***