Bug 1825968 - Stable cluster starts reporting NodeStatusUnknown from master after 72 hours
Summary: Stable cluster starts reporting NodeStatusUnknown from master after 72 hours
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-20 15:28 UTC by Jessica Forrester
Modified: 2020-05-04 11:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 11:50:00 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:50:32 UTC

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


Note You need to log in before you can comment on or make changes to this bug.