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:
Starting and stopping rootless containers with cni networks connected at the same time is not race safe.

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

How reproducible:

Sometimes (depending on the system because it is a race condition)

Steps to Reproduce:
Concurrently start and stop some containers with cni networks as rootless.

Actual results:
It fails sometimes, after the first error all other podman start and stop commands will fail as well. The user has to clean XDG_RUNTIME_DIR in order to get it back working (e.g. systemd session logout or reboot)

Expected results:

Podman should be safe to use concurrently.

Additional info:
Upstream issues: https://github.com/containers/podman/issues/10930, https://github.com/containers/podman/issues/10922
Upstream PR to fix main branch: https://github.com/containers/podman/pull/10939

The upstream fix should be backported to v3.2.

Backport PR https://github.com/containers/podman/pull/10945 has been merged into v3.2.

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:4154