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.

Bug 2124716

Summary: podman kill may deadlock [RHEL 9.1]
Product: Red Hat Enterprise Linux 9 Reporter: Tom Sweeney <tsweeney>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Alex Jia <ajia>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.2CC: atomic-bugs, bbaude, dwalsh, jligon, jnovy, lsm5, mboddu, mheon, pthomas, toneata, tsweeney, umohnani, vrothber, ypu
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-4.2.0-5.el9_1_0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2122599 Environment:
Last Closed: 2022-11-15 15:59:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2122599    
Bug Blocks:    

Comment 2 Tom Sweeney 2022-09-06 22:24:06 UTC 
Can I get a QA and dev ack please for zero day?
Comment 4 Tom Sweeney 2022-09-09 00:12:42 UTC 
@ypu can I get a QA ack please?
Comment 11 Alex Jia 2022-10-20 11:24:55 UTC 
There is no deadlock is found on podman-4.2.0-5.el9_1 with runc-1.1.4-1.el9_1
on on low-performance machine.

cloud-user@test-9-1-0 ~]$ stress -c 13 -i 8 --verbose --timeout 10m &
[cloud-user@test-9-1-0 ~]$ for i in {1..99999}; do sleep 1; uptime;done
 07:19:36 up  1:17,  2 users,  load average: 22.10, 19.73, 14.16
 07:19:37 up  1:17,  2 users,  load average: 22.10, 19.73, 14.16
 07:19:38 up  1:17,  2 users,  load average: 22.01, 19.75, 14.19
 07:19:39 up  1:17,  2 users,  load average: 22.01, 19.75, 14.19
 07:19:40 up  1:17,  2 users,  load average: 22.01, 19.75, 14.19
 07:19:41 up  1:17,  2 users,  load average: 22.01, 19.75, 14.19
 07:19:43 up  1:17,  2 users,  load average: 22.01, 19.79, 14.23
 07:19:44 up  1:17,  2 users,  load average: 22.01, 19.79, 14.23
 07:19:45 up  1:17,  2 users,  load average: 22.01, 19.79, 14.23
 07:19:46 up  1:17,  2 users,  load average: 22.01, 19.79, 14.23
...ignore...

[root@test-9-1-0 ~]# cat ./test.sh
#!/bin/bash

set -o errexit

podman rm -f -i label-for-kill

while true; do
        podman info > /dev/null
        podman run --runtime runc --rm --init --name label-for-kill registry.redhat.io/rhel8/nginx-120 &
        sleep 6
        echo send kill for `pgrep -f label-for-kill`
        kill `pgrep -f label-for-kill`
        sleep 3
done

NOTE: need to login registry.redhat.io firstly.

[root@test-9-1-0 ~]# ./test.sh
...ignore...
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39097
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39231
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39368
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39488
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39619
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39764
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39863
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 39986
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 40121
Trying to pull registry.redhat.io/rhel8/nginx-120:latest...
send kill for 40256
Comment 15 errata-xmlrpc 2022-11-15 15:59:17 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 (Low: podman security, bug fix, and enhancement update), 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-2022:8431