-
Bug
-
Resolution: Done-Errata
-
Critical
-
CentOS Stream 9
-
None
-
passt-0^20240510.g7288448-1.el9
-
None
-
None
-
rhel-sst-virtualization-networking
-
ssg_virtualization
-
1
-
1
-
666
-
QE ack, Dev ack, Docs ack, PXE ack
-
False
-
-
None
-
None
-
None
Current version in CentOS Stream 9 is also affected by https://github.com/containers/podman/issues/22146 / https://github.com/alvistack/passt-top-passt/commit/4988e2b406313c579836dc31867d793cfe77535c
# rpm -qa | grep -E '(podman|passt)'
passt-0^20231204.gb86afe3-1.el9.x86_64
passt-selinux-0^20231204.gb86afe3-1.el9.noarch
podman-5.0.2-1.el9.x86_64
This gives for example issues in gitlab runners, since they are launched with the default network called podman of type bridge.
While manually run containers are using paste network.
Can easily be reproduced (with rootless podman):
$ podman run -it registry.access.redhat.com/ubi9/ubi:latest bash # curl any-large-site-will-stall
This does not work correctly:
$ podman run -it --network podman registry.access.redhat.com/ubi9/ubi:latest bash # curl any-large-site-will-stall
Updating pasta to 20240326.g4988e2b fixes the issue.
- links to
-
RHBA-2024:133650 passt update