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

Bug 1569043

Summary:	A restarted master rejoins as unscheduable
Product:	OpenShift Container Platform	Reporter:	Robert Bost <rbost>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	DeShuai Ma <dma>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.1	CC:	aos-bugs, jokerman, mmccomas, rbost
Target Milestone:	---
Target Release:	3.7.z
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:	2018-05-02 16:39:04 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 Robert Bost 2018-04-18 14:30:15 UTC

Description of problem:

Restarting a master node (like, restarting the host) causes master to rejoin cluster as schedulable even though it was previously marked as unscheduable.


Version-Release number of selected component (if applicable): 3.7.42


How reproducible: Always


Steps to Reproduce:
1. Shut down one master host in multi-master environment. 
2. Wait a bit (~5 minutes? I haven't been able to pin-point exact time)
3. Restart the master host
4. Monitor `oc get nodes -w` to see SchedulingDisabled is never re-added

Actual results: Master is never marked unschedulable again even though it was previously.


Expected results: Master should be marked unscheduable if it was before.

Comment 6 Seth Jennings 2018-05-02 16:39:04 UTC


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