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

Bug 1598362

Summary:	Master node failure causes other nodes to enter NotReady state
Product:	OpenShift Container Platform	Reporter:	David Caldwell <dcaldwel>
Component:	Master	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED DEFERRED	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.9.0	CC:	aos-bugs, dapark, dcaldwel, jokerman, maszulik, mfojtik, mmccomas
Target Milestone:	---
Target Release:	3.9.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-11-20 17:07:52 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 David Caldwell 2018-07-05 08:31:44 UTC

Description of problem:
In a multi-master cluster, when the plug is pulled from a master node, this failure causes other nodes to enter a NotReady state.

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

How reproducible:
Simulate sudden power loss of one master node.


Actual results:
Other nodes go into NotReady.

Expected results:
Cluster should continue as normal.

Additional info:
This is a multi-master, OpenStack environment.

The symptoms sound the same as described in this KCS but it seems that the issue has been fixed: https://access.redhat.com/solutions/3363331

Comment 3 David Caldwell 2018-07-05 08:46:51 UTC

Additional - The node statuses come back to Ready after ~15m.

Comment 7 David Caldwell 2018-09-03 12:16:53 UTC

@Jordan

Sorry - I missed your request for info.

The original version of OpenShift that the customer logged a case against was 3.9.27. They upgraded to 3.9.31 and commented afterwards that the issue appears to have been resolved. Subsequently, they closed their case.

Comment 10 Maciej Szulik 2018-10-04 15:10:57 UTC

David based on comment 7 can we close this BZ?

Comment 11 David Caldwell 2018-11-20 16:33:34 UTC

Yes, please close. 

However, possibly the same/similar issue has returned in 3.11: https://bugzilla.redhat.com/show_bug.cgi?id=1648493

Comment 12 Maciej Szulik 2018-11-20 17:07:52 UTC

Closing based on previous comment.