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.
DescriptionMichele Baldessari
2020-05-29 09:28:19 UTC
Description of problem:
When something kills a running podman exec, we leave a stray ExecIDs for that container which then makes it impossible to remove the container without an "rm -f".
Podman:
$ timeout 5 podman exec redis-bundle-podman-2 sleep 10
$ podman inspect redis-bundle-podman-2 | grep Exec -A3
"ExecIDs": [
"be9319d125048742241cf4e4534ac8ac52c856aaf94eac51f181119bb7c4e902"
],
"GraphDriver": {
$ podman rm redis-bundle-podman-2
Error: cannot remove container 7ff933b3b4317bf2e05de5cccc799e8b1596b994aa3afa199fd0ca74e4b9c044 as it has active exec sessions: container state improper
Version-Release number of selected component (if applicable):
podman-1.6.4-11.module+el8.2.0+6369+1f4293b4.x86_64
Mike Burns - Please confirm that we have agreement from OSP to delay 1841485 until RHEL 8.4, Apr-2021. It is not clear from the recent comments that everyone on OSP has agreed that is OK.
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 (Moderate: container-tools:rhel8 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-2021:1796
Description of problem: When something kills a running podman exec, we leave a stray ExecIDs for that container which then makes it impossible to remove the container without an "rm -f". Podman: $ timeout 5 podman exec redis-bundle-podman-2 sleep 10 $ podman inspect redis-bundle-podman-2 | grep Exec -A3 "ExecIDs": [ "be9319d125048742241cf4e4534ac8ac52c856aaf94eac51f181119bb7c4e902" ], "GraphDriver": { $ podman rm redis-bundle-podman-2 Error: cannot remove container 7ff933b3b4317bf2e05de5cccc799e8b1596b994aa3afa199fd0ca74e4b9c044 as it has active exec sessions: container state improper Version-Release number of selected component (if applicable): podman-1.6.4-11.module+el8.2.0+6369+1f4293b4.x86_64