Bug 1855003 - cri-o image GC stops on worker nodes when orphaned layers are found
Summary: cri-o image GC stops on worker nodes when orphaned layers are found
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.5
Hardware: All
OS: All
Target Milestone: ---
: ---
Assignee: Peter Hunt
QA Contact: Sunil Choudhary
Depends On:
TreeView+ depends on / blocked
Reported: 2020-07-08 15:39 UTC by Dan Yocum
Modified: 2024-06-13 22:46 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-09-22 15:31:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Dan Yocum 2020-07-08 15:39:29 UTC
Description of problem:

When orphaned or "broken" (i.e., partial layer files) are found on a worker node container directory, cri-o garbage collection halts, allowing the FS to fill up and crashes the node.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. start to deploy a pod and "yank the power cord" to create a partial layer file on a worker node
2. When rebooted, GC halts when it encounters a partial/broken/orphaned image layer

Actual results:


Expected results:


Additional info:

Comment 9 Harshal Patil 2020-07-17 16:17:39 UTC

*** This bug has been marked as a duplicate of bug 1857224 ***

Comment 20 Tom Sweeney 2020-10-27 20:14:25 UTC
Nalin, any further comments on progress on this one?

Comment 29 Qi Wang 2021-03-18 19:05:21 UTC
Did not get completed this sprint.

Comment 30 Qi Wang 2021-04-09 19:51:20 UTC
Did not get completed this sprint.

Comment 31 Qi Wang 2021-06-07 18:39:48 UTC
container/storage PR https://github.com/containers/storage/pull/898 and https://github.com/containers/storage/pull/926 might fix this bug. Is there a way we can reproduce and test it does work?

Comment 32 Michael Washer 2021-06-20 22:58:27 UTC
The only way that I am I am aware has been used to re-create the issue is by performing the following, during an image pull.
echo b >/proc/sysrq-trigger

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