Bug 1948052 - Kubelet got stuck on worker, causing thrashing and node not-ready
Summary: Kubelet got stuck on worker, causing thrashing and node not-ready
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.8.0
Assignee: Harshal Patil
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-09 21:12 UTC by Gabriel Diotte
Modified: 2024-10-01 17:53 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-03 14:35:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5853471 0 None None None 2021-04-20 16:17:52 UTC

Comment 1 Maciej Szulik 2021-04-12 15:07:19 UTC 
Moving this over to node/kubelet team to further investigate, since this doesn't look like a scheduler problem.
Comment 9 Andrew Beekhof 2021-04-19 00:37:22 UTC 
A reasonably simple improvement to kubelet's healthz checks would have prevented the node from becoming wedged.
Unfortunately there doesn't seem to be much interest merging the PR that implements it.

   https://github.com/kubernetes/kubernetes/issues/98981
   https://github.com/kubernetes/kubernetes/pull/94210
Comment 26 Red Hat Bugzilla 2023-09-15 01:04:55 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.