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.
Bug 1752599 - Deadlock when pulling an image is interrupted
Summary: Deadlock when pulling an image is interrupted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1734578 1779834
TreeView+ depends on / blocked
 
Reported: 2019-09-16 18:02 UTC by Matthew Heon
Modified: 2020-11-14 07:34 UTC (History)
12 users (show)

Fixed In Version: podman-1.6.3-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1779834 (view as bug list)
Environment:
Last Closed: 2020-02-04 12:26:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:0348 0 None None None 2020-02-04 12:27:28 UTC

Description Matthew Heon 2019-09-16 18:02:22 UTC 
Description of problem:

Originally filed as BZ1748682 against Openshift 4.2.

When a `podman pull` command is interrupted (in the case of the original bug, by a reboot) while it is in certain critical sections, the containers/storage library will attempt to clean up the partially-completed operation if the pull is re-ran. This code path can attempt to take a lock multiple times, resulting in a deadlock that will prevent almost all Podman commands from running (and any command requiring c/storage - Buildah, CRI-O, Skopeo will also be unable to stop.

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

Podman 1.4.2-stable2 (should reproduce on any released Podman)

How reproducible:

Fairly reproducible when `podman pull` is run as a systemd service on bootup, but this is a race condition with a fairly slim window - will be difficult to hit in normal use.

Steps to Reproduce:
1. podman pull <image>
2. Interrupt previous `podman pull` command while pull is in progress - SIGKILL should work
3. Re-run `podman pull <image>`

Actual results:

Second `podman pull` command freezes. Until it is closed, Podman, Skopeo, and CRI-O cannot launch successfully. Killing the frozen process will restore operation, but running the same `podman pull` again can potentially freeze again.

Expected results:

Second `podman pull` completes normally

Additional info:

Likelihood of triggering is low under normal circumstances, but Openshift found a fairly reliable way of doing it.
Comment 2 Daniel Walsh 2019-09-16 19:20:36 UTC 
Is this a podman bug or a containers/storage bug?
Comment 3 Matthew Heon 2019-09-16 19:30:15 UTC 
Bug is in c/storage. Fixed in 1.13.3. Will be vendored into Podman 1.6.0.
Comment 12 errata-xmlrpc 2020-02-04 12:26:32 UTC 
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/RHSA-2020:0348
Note You need to log in before you can comment on or make changes to this bug.