Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pasta: UDP port range forwarding: hang in podman logs #24272

Open
edsantiago opened this issue Oct 15, 2024 · 1 comment
Open

pasta: UDP port range forwarding: hang in podman logs #24272

edsantiago opened this issue Oct 15, 2024 · 1 comment
Labels
flakes Flakes from Continuous Integration pasta pasta(1) bugs or features

Comments

@edsantiago
Copy link
Member

Very infrequent. I can't tell if it's parallel-related or not:


not ok 344 |505| UDP port range forwarding, IPv4, tap in 122187ms
         # tags: ci:parallel
         # (from function `run_podman' in file test/system/[helpers.bash, line 561](https://github.com/containers/podman/blob/94dcf76eb2d65c5f5a40f83d855cd17ef6655cc3/test/system/helpers.bash#L561),
         #  from function `pasta_test_do' in file test/system/[505-networking-pasta.bats, line 252](https://github.com/containers/podman/blob/94dcf76eb2d65c5f5a40f83d855cd17ef6655cc3/test/system/505-networking-pasta.bats#L252),
         #  in test file test/system/[505-networking-pasta.bats, line 609](https://github.com/containers/podman/blob/94dcf76eb2d65c5f5a40f83d855cd17ef6655cc3/test/system/505-networking-pasta.bats#L609))
         #   `pasta_test_do' failed
         #
<+     > # $ podman info --format {{.Host.Pasta.Executable}}
<+246ms> # /usr/bin/pasta
         #
<+357ms> # $ podman run -d --name=c-socat-t344-mdzgdmfm --net=pasta -p [10.128.15.220]:5157-5159:5157-5159/udp quay.io/libpod/testimage:20240123 sh -c for port in $(seq 5157 5159); do                              socat -u UDP4-LISTEN:${port},null-eof STDOUT &                          done; wait
<+378ms> # f69bae53762f567446cb332ae6b6c1e91cea4ae2cc74c4f10583d84a80c83ce8
         #
<+036ms> # $ podman exec c-socat-t344-mdzgdmfm ss -Hln -4 --udp sport = 5157
<+159ms> # UNCONN 0      0      0.0.0.0:5157 0.0.0.0:*
         #
<+035ms> # $ podman exec c-socat-t344-mdzgdmfm ss -Hln -4 --udp sport = 5158
<+171ms> # UNCONN 0      0      0.0.0.0:5158 0.0.0.0:*
         #
<+030ms> # $ podman exec c-socat-t344-mdzgdmfm ss -Hln -4 --udp sport = 5159
<+233ms> # UNCONN 0      0      0.0.0.0:5159 0.0.0.0:*
         #
<+062ms> # $ podman logs --follow c-socat-t344-mdzgdmfm
<+0120s> # timeout: sending signal TERM to command ‘/var/tmp/go/src/github.com/containers/podman/bin/podman’

The podman logs --follow blocks until the container terminates. It looks like the container is not terminating.

x x x x x x
sys(2) podman(2) debian-13(1) rootless(2) host(2) sqlite(1)
fedora-40(1) boltdb(1)
@edsantiago edsantiago added flakes Flakes from Continuous Integration pasta pasta(1) bugs or features labels Oct 15, 2024
@sbrivio-rh
Copy link
Collaborator

Hopefully the same as #24147, but I can't reproduce that with these tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakes Flakes from Continuous Integration pasta pasta(1) bugs or features
Projects
None yet
Development

No branches or pull requests

2 participants