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

Bug 1825968

Summary:	Stable cluster starts reporting NodeStatusUnknown from master after 72 hours
Product:	OpenShift Container Platform	Reporter:	Jessica Forrester <jforrest>
Component:	Node	Assignee:	Ryan Phillips <rphillips>
Status:	CLOSED ERRATA	QA Contact:	Sunil Choudhary <schoudha>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, jokerman, rphillips, scuppett, zyu
Target Milestone:	---
Target Release:	4.4.0
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:	2020-05-04 11:50:00 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 Jessica Forrester 2020-04-20 15:28:59 UTC

On a 4.4.0.rc8 cluster, after 72 hours post-install the kubelet on master-0 stopped reporting back. Resulting in the node reporting NodeStatusUnknown and the node going NotReady. Nothing was happening on this cluster over the weekend, and very little had been touched on it from an OOTB AWS installation. I believe the only changes were to configure an alert manager receiver.

Comment 10 errata-xmlrpc 2020-05-04 11:50:00 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581