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

Bug 1584471

Summary:	[3.5] All nodes got NotReady with network hiccups
Product:	OpenShift Container Platform	Reporter:	Takayoshi Kimura <tkimura>
Component:	Master	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED DUPLICATE	QA Contact:	Wang Haoran <haowang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.5.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:	2019-03-07 11:20:26 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 Takayoshi Kimura 2018-05-31 02:01:53 UTC

Description of problem:

All nodes got NotReady status with few sec (like 5 sec, definitely not 40+ sec) network outage and the symptom is very similar to the following upstream k8s stuck TCP connection issue.

https://github.com/kubernetes/kubernetes/issues/48638

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

v3.5.5.31.66

How reproducible:

Rarely, logs indicated there is few sec network hiccups

Steps to Reproduce:
1.
2.
3.

Actual results:

Node keeps Ready status

Expected results:

All nodes unexpectedly got NotReady status

Additional info:

Comment 4 Michal Fojtik 2019-03-07 11:20:26 UTC


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