Bug 1982762

Summary:	podman v3.2.2 - race condition with rootless cni networking
Product:	Red Hat Enterprise Linux 8	Reporter:	Paul Holzinger <pholzing>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	Yuhui Jiang <yujiang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	acui, bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, tsweeney, umohnani, ypu
Target Milestone:	beta	Flags:	acui: needinfo+ pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman-3.3.0-0.13.el8 or newer	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 17:40:16 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:

Description Paul Holzinger 2021-07-15 16:08:09 UTC

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.

Comment 1 Paul Holzinger 2021-07-16 08:38:57 UTC

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

Comment 11 errata-xmlrpc 2021-11-09 17:40:16 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 (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