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 2097049

Summary: ERRO[0009] Error forwarding signal 18 to container using rootless user with timeout+sleep in the podman run command [rhel-8.6.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Alex Jia <ajia>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.6CC: bbaude, ddarrah, dornelas, dwalsh, falim, fsayyed, jligon, jnovy, lsm5, mheon, pghadge, pthomas, umohnani, ypu
Target Milestone: rcKeywords: ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: podman-4.1.1-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2090609 Environment:
Last Closed: 2022-08-02 10:05:42 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: 2090609    
Bug Blocks:    

Comment 4 Alex Jia 2022-06-28 08:51:48 UTC 
I can reproduce this bug with the following reproducer on podman-4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64.

[root@kvm-05-guest11 ~]# yes | head -10 | xargs --replace -P5 timeout 2 podman run --rm --init ubi8 sleep 5
ERRO[0000] container not running                        
ERRO[0002] forwarding signal 18 to container fc0d770143e05ba998b3e45e4e5403582ea18f67b96f3fe75d7c1caa1efdc3c6: error sending signal to container fc0d770143e05ba998b3e45e4e5403582ea18f67b96f3fe75d7c1caa1efdc3c6: `/usr/bin/runc kill fc0d770143e05ba998b3e45e4e5403582ea18f67b96f3fe75d7c1caa1efdc3c6 18` failed: exit status 1 

And verified on podman-4.0.2-7.module+el8.6.0+15634+64c2e3db.x86_64 and podman-4.1.1-1.module+el8.6.0+15659+f3ff693b.x86_64.

1. podman-4.0.2-7.module+el8.6.0+15634+64c2e3db.x86_64
[root@kvm-05-guest11 ~]# rpm -q podman runc systemd kernel
podman-4.0.2-7.module+el8.6.0+15634+64c2e3db.x86_64
runc-1.0.3-2.module+el8.6.0+15634+64c2e3db.x86_64
systemd-239-58.el8_6.2.x86_64
kernel-4.18.0-372.15.1.el8_6.x86_64
[root@kvm-05-guest11 ~]# yes | head -10 | xargs --replace -P5 timeout 2 podman run --rm --init ubi8 sleep 5
[root@kvm-05-guest11 ~]# podman ps -a
CONTAINER ID  IMAGE                                   COMMAND     CREATED         STATUS      PORTS       NAMES
63ca823cc994  registry.access.redhat.com/ubi8:latest  sleep 5     14 seconds ago  Created                 nostalgic_aryabhata
400d19738519  registry.access.redhat.com/ubi8:latest  sleep 5     14 seconds ago  Created                 confident_pasteur
2e8b41f2a6c0  registry.access.redhat.com/ubi8:latest  sleep 5     14 seconds ago  Created                 xenodochial_faraday
930cbf8413d7  registry.access.redhat.com/ubi8:latest  sleep 5     13 seconds ago  Created                 hopeful_feistel
6091b7552155  registry.access.redhat.com/ubi8:latest  sleep 5     12 seconds ago  Created                 stupefied_turing


2. podman-4.1.1-1.module+el8.6.0+15659+f3ff693b.x86_64
[root@kvm-05-guest11 ~]# rpm -q podman runc systemd kernel
podman-4.1.1-1.module+el8.6.0+15659+f3ff693b.x86_64
runc-1.0.3-2.module+el8.6.0+15634+64c2e3db.x86_64
systemd-239-58.el8_6.2.x86_64
kernel-4.18.0-372.15.1.el8_6.x86_64
[root@kvm-05-guest11 ~]# yes | head -10 | xargs --replace -P5 timeout 2 podman run --rm --init ubi8 sleep 5
[root@kvm-05-guest11 ~]# podman ps -a
CONTAINER ID  IMAGE                                   COMMAND     CREATED         STATUS      PORTS       NAMES
b992e340ab35  registry.access.redhat.com/ubi8:latest  sleep 5     35 seconds ago  Created                 brave_ptolemy
8793f80a0c31  registry.access.redhat.com/ubi8:latest  sleep 5     35 seconds ago  Created                 elastic_lederberg
18646094a85d  registry.access.redhat.com/ubi8:latest  sleep 5     35 seconds ago  Created                 hungry_panini
7816cdfa527d  registry.access.redhat.com/ubi8:latest  sleep 5     35 seconds ago  Created                 quizzical_driscoll
aba8e937c200  registry.access.redhat.com/ubi8:latest  sleep 5     35 seconds ago  Created                 pedantic_sutherland
44c6d0d1de96  registry.access.redhat.com/ubi8:latest  sleep 5     33 seconds ago  Created                 optimistic_dewdney
a6dda13b7445  registry.access.redhat.com/ubi8:latest  sleep 5     33 seconds ago  Created                 silly_wiles
Comment 10 Alex Jia 2022-07-19 02:54:16 UTC 
This bug has been verified on podman-4.1.1-2.module+el8.6.0+15917+093ca6f8.

[root@sweetpig-22 ~]# rpm -q podman runc systemd kernel
podman-4.1.1-2.module+el8.6.0+15917+093ca6f8.x86_64
runc-1.1.3-2.module+el8.6.0+15917+093ca6f8.x86_64
systemd-239-58.el8_6.3.x86_64
kernel-4.18.0-372.18.1.el8_6.x86_64

[root@sweetpig-22 ~]# podman images
REPOSITORY                       TAG         IMAGE ID      CREATED      SIZE
registry.access.redhat.com/ubi8  latest      2fd9e1478809  4 weeks ago  225 MB

[root@sweetpig-22 ~]# yes | head -10 | xargs --replace -P5 timeout 2 podman run --rm --init ubi8 sleep 5
ERRO[0000] container not running                        
ERRO[0000] container not running                        
ERRO[0000] container not running                        
ERRO[0000] container not running                        
ERRO[0000] container not running  
                      
[root@sweetpig-22 ~]# podman ps -a
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

[root@sweetpig-22 ~]# timeout 4 podman run --log-level=info -i --rm registry.redhat.io/ansible-automation-platform-21/ee-supported-rhel8 python3 -c 'import time; time.sleep(5)'
INFO[0000] podman filtering at log level info           
INFO[0000] Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled 
INFO[0000] Setting parallel job count to 7              
Trying to pull registry.redhat.io/ansible-automation-platform-21/ee-supported-rhel8:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 0d725b91398e [--------------------------------------] 0.0b / 1.7KiB
Copying blob 1e09a5ee0038 [--------------------------------------] 0.0b / 34.7MiB
Copying blob efe94c0f6ff6 [--------------------------------------] 0.0b / 189.4MiB
Copying blob 47c1fb849539 [--------------------------------------] 0.0b / 19.9MiB
Copying blob 971ebcb22551 [--------------------------------------] 0.0b / 65.6MiB
INFO[0003] Received shutdown signal "terminated", terminating!  PID=21196
INFO[0003] Invoking shutdown handler "libpod"            PID=21196
Comment 14 errata-xmlrpc 2022-08-02 10:05:42 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 (container-tools:rhel8 bug fix 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/RHBA-2022:5824