Bug 1737310 - Nodes are going into 'NotReady' state again and again in AWS environment
Summary: Nodes are going into 'NotReady' state again and again in AWS environment
Keywords:
Status: CLOSED DUPLICATE of bug 1727140
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Seth Jennings
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-05 05:44 UTC by Nitin Goyal
Modified: 2019-08-06 19:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-05 16:55:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nitin Goyal 2019-08-05 05:44:23 UTC 
Description of problem:
Nodes are going into NotReady state due to container runtime is down (IN AWS only).

Version-Release number of selected component (if applicable):
$ oc version 
oc v3.11.129
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://master.refarch.nigoyal.com:443
openshift v3.11.129
kubernetes v1.11.0+d4cacc0


How reproducible:


Steps to Reproduce:
1. Create a setup in AWS
2.
3.

Actual results:
Nodes are going into NotReady state again and again.

Expected results:
Nodes should not go into NotReady state.

Additional info:
Comment 2 Seth Jennings 2019-08-05 16:55:11 UTC 
Very likely a dup of 1727140.  It isn't that the container runtime (docker) is down.  It is that atomic-openshift-node.service is restarting due to a bug in the sync pod.

*** This bug has been marked as a duplicate of bug 1727140 ***
Note You need to log in before you can comment on or make changes to this bug.