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:

This BZ is a spinoff from https://bugzilla.redhat.com/show_bug.cgi?id=1699202 . The investigation in the original kernel leak bug has shown that another leak occurred during the creation/destruction cycle of podman containers.

The upstream review meant to fix this leak is here: 
https://github.com/containers/libpod/pull/3551

The aim of this BZ is to A) track the fix in podman and B) separate this issue from the other analysis going on in rhbz#1699202

Can reproduce this with podman-1.1.0-1.git006206a.module+el8+2851+dbc75b3b.x86_64. Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64, the exist file is already not show up in the tmpfs /run/libpod/exist. Details:
# podman run --name test -d busybox
d3708281a63cb8437091a25d5f207a36d52266822467362e9d7afbd60730e8c3
# ls /run/libpod/exits/

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-2019:3403