Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPasi Karkkainen
2021-03-25 19:33:46 UTC
Description of problem:
It seems there's some sort of regression in the latest versions docker-1.13.1-203.git0be3e21.el7 and docker-1.13.1-204.git0be3e21.el7. Docker seems to crash / get stuck when trying to run a kubelet container.
After trying to start a kubelet container commands like "docker ps" or any other docker cli command won't work anymore, they just get stuck waiting forever. docker seems to crash.
Also "systemctl restart docker" won't work and will wait forever.
Downgrading docker to older version 1.13.1-162.git64e9980.el7 seems to fix the problem, and kubelet works OK with the docker -162 version.
selinux is enabled in enforcing mode.
Version-Release number of selected component (if applicable):
docker-1.13.1-203.git0be3e21.el7 and docker-1.13.1-204.git0be3e21.el7
How reproducible:
Always
Steps to Reproduce:
1. try to run kubelet in docker container
2. docker gets stuck / crashes.
Actual results:
docker gets stuck / crashes when kubelet starts.
Expected results:
kubelet works OK just like with the older docker -162 version.
Additional info:
After trying to run kubelet and thus docker has crashed then it's impossible to do anything docker related..
"systemctl stop docker" seems to complete, but all the docker-containerd-shim-current / docker-runc-current processes are left behind. If one kills the processes and tries to restart docker daemon then they just re-appear and get stuck again.
"systemctl start docker" won't work and will block/wait forever.
Problem can be reproduced 100% every time by using rke to install kubernetes cluster on el7 nodes. Example versions: rke v1.2.4 and kubernetes v1.18.14 and v1.19.6, but the same problem seems to happen also with other rke/kubernetes versions.
Based on all of Robb's testing (see BZ#1943700 & 1896883#c17) I believe this is the same root cause as Bug 1896883
*** This bug has been marked as a duplicate of bug 1896883 ***