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): 4.4.4 How reproducible: always 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 3. Actual results: Fail Expected results: Succeed Additional info:
*** This bug has been marked as a duplicate of bug 1857224 ***
Nalin, any further comments on progress on this one?
Did not get completed this sprint.
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?
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 ```