Bug 1584471 - [3.5] All nodes got NotReady with network hiccups
Summary: [3.5] All nodes got NotReady with network hiccups
Keywords:
Status: CLOSED DUPLICATE of bug 1572622
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.z
Assignee: Michal Fojtik
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 02:01 UTC by Takayoshi Kimura
Modified: 2021-09-09 14:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-07 11:20:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.