Bug 2060494 - Fix inotify leak and kubelet retaining memory
Summary: Fix inotify leak and kubelet retaining memory
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.6.z
Hardware: Unspecified
OS: All
Target Milestone: ---
: 4.8.z
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
: 2039205 2040680 2040931 2042175 (view as bug list)
Depends On: 2044438 2060515
Blocks: 2042175 2060528
TreeView+ depends on / blocked
Reported: 2022-03-03 15:43 UTC by Ryan Phillips
Modified: 2023-09-15 01:52 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2044438
: 2060528 (view as bug list)
Last Closed: 2022-03-16 11:30:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 1203 0 None Merged [release-4.8] Bug 2060494: Backports inotify leak fix into kubelet 2022-03-28 13:41:24 UTC
Red Hat Product Errata RHBA-2022:0795 0 None None None 2022-03-16 11:30:57 UTC

Comment 4 Neelesh Agrawal 2022-03-04 18:24:56 UTC
*** Bug 2042175 has been marked as a duplicate of this bug. ***

Comment 5 Sunil Choudhary 2022-03-08 05:02:25 UTC
This is upstream fix which is now merged. Marking it verified.

Comment 8 errata-xmlrpc 2022-03-16 11:30:45 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 (OpenShift Container Platform 4.8.34 bug fix update), and where to find the updated
files, follow the link below.

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


Comment 9 Christoffer Back 2022-03-17 06:30:48 UTC
*** Bug 2039205 has been marked as a duplicate of this bug. ***

Comment 11 W. Trevor King 2022-03-21 22:46:16 UTC
Now that 4.8.34 has a public errata, 4.8.25 -> 4.8.34 updates are recommended in fast-4.8:

$ CHANNEL=fast-4.8 hack/available-updates.sh 4.8.25 | tail -n1
4.8.34  quay.io/openshift-release-dev/ocp-release@sha256:016a1e055bc839623abb4d4808f4135ee37b97dcf5b5cf4a586519450e6acbc8       https://access.redhat.com/errata/RHBA-2022:0795

fast-4.8 is fully supported [1].  In the absence of an UpgradeBlocker bug turning up [2], the update recommendation will appear in stable-4.8 after a delay for collecting and processing feedback [3].

[1]: https://docs.openshift.com/container-platform/4.8/updating/understanding-upgrade-channels-release.html#fast-version-channel_understanding-upgrade-channels-releases
[2]: https://github.com/openshift/enhancements/tree/master/enhancements/update/update-blocker-lifecycle
[3]: https://docs.openshift.com/container-platform/4.8/updating/understanding-upgrade-channels-release.html#stable-version-channel_understanding-upgrade-channels-releases

Comment 17 Ryan Phillips 2022-04-01 17:28:00 UTC
*** Bug 2040680 has been marked as a duplicate of this bug. ***

Comment 18 Ryan Phillips 2022-04-01 17:34:40 UTC
*** Bug 2040931 has been marked as a duplicate of this bug. ***

Comment 23 Neelesh Agrawal 2022-04-25 16:43:38 UTC
There is another upstream Kubernetes/Kubelet memory leak found and is being tracked by

If a customer is affected by symptoms of kubelet memory leak even after applying fix for this BZ, it is worth checking-out the above BZ. With the help of pprof collected, there is a way to confirm the cause of the leak.

If you do confirm that your customer is affected by the new BZ, please move the case the above BZ. There is no plan to reopen this BZ as the underlying leak is fixed and new leaks need separate tracking.

Comment 25 Red Hat Bugzilla 2023-09-15 01:52:30 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days

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