Hide Forgot
Description of problem: Image Garbage collection is trying to delete images in use by stopped containers. journalctl_--no-pager_--unit_docker:Apr 30 15:25:14 drlosn05.example.com dockerd-current[1521]: time="2018-04-30T15:25:14.524633778+12:00" level=error msg="Handler for DELETE /v1.24/images/sha256:41ad666f e1b52e4a5ee47042bb3e6f53a3ae9cec6edf86960b1337de8e07d651 returned error: conflict: unable to delete 41ad666fe1b5 (must be forced) - image is being used by stopped container 7ea6cb10acce" journalctl_--no-pager_--unit_docker:Apr 30 15:25:14 drlosn05.example.com dockerd-current[1521]: time="2018-04-30T15:25:14.524780645+12:00" level=error msg="Handler for DELETE /v1.24/images/sha256:41ad666f e1b52e4a5ee47042bb3e6f53a3ae9cec6edf86960b1337de8e07d651 returned error: conflict: unable to delete 41ad666fe1b5 (must be forced) - image is being used by stopped container 7ea6cb10acce" journalctl_--no-pager_--unit_docker:Apr 30 15:25:14 drlosn05.example.com dockerd-current[1521]: time="2018-04-30T15:25:14.545644810+12:00" level=error msg="Handler for DELETE /v1.24/images/sha256:d58c2b65 f4d51dbe67ce04a247f38d2169b078306469ed64ead077a1d6df031a returned error: conflict: unable to delete d58c2b65f4d5 (must be forced) - image is being used by stopped container 0aaec7ec9df2" journalctl_--no-pager_--unit_docker:Apr 30 15:25:14 drlosn05.example.com dockerd-current[1521]: time="2018-04-30T15:25:14.545735698+12:00" level=error msg="Handler for DELETE /v1.24/images/sha256:d58c2b65 f4d51dbe67ce04a247f38d2169b078306469ed64ead077a1d6df031a returned error: conflict: unable to delete d58c2b65f4d5 (must be forced) - image is being used by stopped container 0aaec7ec9df2" Version-Release number of selected component (if applicable): ansible-2.4.2.0-2.el7.noarch openshift-ansible-3.4.95-1.git.0.3c99da3.el7.noarch atomic-openshift-3.6.173.0.113-1.git.0.65fb9fb.el7.x86_64 Actual results: Images in use by the stopped containers are being considered by GC for deletion. Expected results: Images in use should not be included in the images evaluated for deletion. Additional info: https://github.com/kubernetes/kubernetes/pull/57020 Issue reported here: https://github.com/kubernetes/kubernetes/issues/54440
Attached the node-config.yaml file as well for GC config and other settings.
Created attachment 1447795 [details] node.log
Verify on v3.10.0-0.58.0 detail log see the attached log.
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-2018:1816