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.
Description of problem:
During a normal openshift-ansible upgrade, node has failed to drain during an upgrade. oc adm drain has been hung for over an hour.
Version-Release number of selected component (if applicable):
Master: 3.10.7
Node: 3.10.2
Additional info:
- `docker ps` is responsive
- node is of type 'infra'
- See attachments for listings
This happens when I run docker CLI commands as well:
# docker exec -ti f29ea91a13da /bin/sh
rpc error: code = 14 desc = grpc: the connection is unavailable
containerd has died again. dockerd-current is running and the docker-containerd-shim-current processes for existing conatiners are running, but containerd is not running.
Looking at the logs I see the stack trace from containerd when it died (see next attachment).
Over to Containers.
QE can't reproduce it and never met it when do 3.10 upgrade testing.
Hi Justin, Could you try if the latest docker version fir your issue and verify the bug? thanks