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

sdnotify test: podman wait: hangs #15800

Closed
edsantiago opened this issue Sep 14, 2022 · 4 comments
Closed

sdnotify test: podman wait: hangs #15800

edsantiago opened this issue Sep 14, 2022 · 4 comments
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

New flake seen in f36 rootless:

[+1429s] not ok 305 sdnotify : play kube - with policies
         # (from function `run_podman' in file test/system/[helpers.bash, line 207](https://github.com/containers/podman/blob/dd53ee59988d49a892fde7a86e41ef636f9814aa/test/system/helpers.bash#L207),
         #  in test file test/system/[260-sdnotify.bats, line 342](https://github.com/containers/podman/blob/dd53ee59988d49a892fde7a86e41ef636f9814aa/test/system/260-sdnotify.bats#L342))
         #   `run_podman container wait $container_a' failed
         # $ podman rm -t 0 --all --force --ignore
         # $ podman ps --all --external --format {{.ID}} {{.Names}}
         # $ podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
         # quay.io/libpod/testimage:20220615 f26aa69bb3f3
         # $ podman pull quay.io/libpod/fedora:31
         # Trying to pull quay.io/libpod/fedora:31...
         # Getting image source signatures
         # Copying blob sha256:c28ace6b0c4ae099f6f81091731bdf41d9771d28bad96ae4a3507fe950560930
         # Copying config sha256:a7a37f74ff864eec55891b64ad360d07020827486e30a92ea81d16459645b26a
         # Writing manifest to image destination
         # Storing signatures
         # a7a37f74ff864eec55891b64ad360d07020827486e30a92ea81d16459645b26a
         # $ podman container wait test_pod-a test_pod-b --condition=running
         # Error: no container with name or ID "test_pod-a" found: no such container
         # [ rc=125 ]
         # $ podman ps -a
         # CONTAINER ID  IMAGE                                        COMMAND     CREATED                 STATUS      PORTS       NAMES
         # 8afb597b4654  localhost/podman-pause:4.3.0-dev-1663157913              Less than a second ago  Created                 9cffc8377ee1-service
         # 6c9d131429af  localhost/podman-pause:4.3.0-dev-1663157913              Less than a second ago  Created                 53ad1b768e5f-infra
         # $ podman container wait test_pod-a test_pod-b --condition=running
         # Error: no container with name or ID "test_pod-a" found: no such container
         # [ rc=125 ]
         # $ podman ps -a
         # CONTAINER ID  IMAGE                                        COMMAND     CREATED                 STATUS      PORTS       NAMES
         # 8afb597b4654  localhost/podman-pause:4.3.0-dev-1663157913              Less than a second ago  Created                 9cffc8377ee1-service
         # 6c9d131429af  localhost/podman-pause:4.3.0-dev-1663157913              Less than a second ago  Created                 53ad1b768e5f-infra
         # 10dccf1282bc  quay.io/libpod/fedora:31                                 Less than a second ago  Created                 test_pod-a
         # $ podman container wait test_pod-a test_pod-b --condition=running
         # Error: no container with name or ID "test_pod-b" found: no such container
         # [ rc=125 ]
         # $ podman ps -a
         # CONTAINER ID  IMAGE                                        COMMAND     CREATED                 STATUS                     PORTS       NAMES
         # 8afb597b4654  localhost/podman-pause:4.3.0-dev-1663157913              1 second ago            Up Less than a second ago              9cffc8377ee1-service
         # 6c9d131429af  localhost/podman-pause:4.3.0-dev-1663157913              1 second ago            Up Less than a second ago              53ad1b768e5f-infra
         # 10dccf1282bc  quay.io/libpod/fedora:31                                 1 second ago            Up Less than a second ago              test_pod-a
         # 10a2c0df9a40  quay.io/libpod/testimage:20220615                        Less than a second ago  Up Less than a second ago              test_pod-b
         # $ podman container wait test_pod-a test_pod-b --condition=running
         # -1
         # -1
         # $ podman container inspect test_pod-a test_pod-b 9cffc8377ee1-service --format {{.Config.SdNotifyMode}}
         # container
         # conmon
         # ignore
         # /var/tmp/go/src/github.com/containers/podman/test/system/260-sdnotify.bats: line 326: /tmp/podman_bats.v90amR/socat.log: No such file or directory
         # $ podman container inspect test_pod-a --format {{.Config.SdNotifySocket}}
         # /var/tmp/-podman-notify-proxy.sock1715659030
         # $ podman logs test_pod-a
         # /run/notify/notify.sock
         # READY
         # $ podman exec test_pod-a /bin/touch /stop
         # $ podman container inspect 9cffc8377ee1-service --format {{.State.ConmonPid}}
         # 100133
         # $ podman container wait test_pod-a
         # timeout: sending signal TERM to command ‘/var/tmp/go/src/github.com/containers/podman/bin/podman’
         # [ rc=124 (** EXPECTED 0 **) ]
         # *** TIMED OUT ***

That is, podman container wait is hanging. Code:

run_podman container wait $container_a

Looking at flake logs, first logged instance was on Monday:

[sys] 304 sdnotify : play kube - with policies

@edsantiago edsantiago added the flakes Flakes from Continuous Integration label Sep 14, 2022
@edsantiago
Copy link
Member Author

All right kids, this one's getting trendy[1]. Here we go again, still f36 rootless.

[1] for purposes of this discussion, "trendy" is not considered a Good Thing.

@vrothberg
Copy link
Member

I'll take a look. Thanks, Ed!

@edsantiago
Copy link
Member Author

@vrothberg
Copy link
Member

Thanks, Ed! #15820 should fix it.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

2 participants