Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1608742

Summary:	[admin] Better add "SchedulingDisabled" status for nodes marked as un-schedulable
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	bpeterse
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas, spadgett, yapei
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-28 13:55:56 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 Yadan Pei 2018-07-26 08:59:16 UTC

Description of problem:
It's better to add "SchedulingDisabled" status for nodes marked as un-schedulable  

Version-Release number of selected component (if applicable):
openshift v3.11.0-0.9.0


How reproducible:
Always

Steps to Reproduce:
1.Go to Administration -> Nodes page
2.Select one Node "qe-ui-311-node-1" and Mark it as Unschedulable
3.

Actual results:
2. Node Status is still show Ready

Expected results:
2. It's better if we could show Ready,SchedulingDisabled as in CLI
# oc get node
NAME                               STATUS                     ROLES     AGE       VERSION
qe-ui-311-master-etcd-1            Ready                      master    6h        v1.11.0+d4cacc0
qe-ui-311-node-1                   Ready,SchedulingDisabled   compute   5h        v1.11.0+d4cacc0


Additional info:

Comment 1 bpeterse 2018-07-27 03:05:34 UTC

PR opened https://github.com/openshift/console/pull/322

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


*** This bug has been marked as a duplicate of bug 1748405 ***