Bug 1737310

Summary:	Nodes are going into 'NotReady' state again and again in AWS environment
Product:	OpenShift Container Platform	Reporter:	Nitin Goyal <nigoyal>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED DUPLICATE	QA Contact:	Sunil Choudhary <schoudha>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	3.11.0	CC:	aos-bugs, jokerman, knarra
Target Milestone:	---
Target Release:	3.11.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-08-05 16:55:11 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 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 ***