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.

Sign up for GitHub

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

Jump to bottom

ci: stop podman.service test: connection refused #17940

Closed
edsantiago opened this issue Mar 27, 2023 · 1 comment · Fixed by #18527
Closed

ci: stop podman.service test: connection refused #17940

edsantiago opened this issue Mar 27, 2023 · 1 comment · Fixed by #18527
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. 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 

stop podman.service
...
Execing /usr/bin/systemd-socket-activate [...] --listen 127.0.0.1:43255 [...]/bin/podman system service --time=0

Execing bin/podman-remote --url tcp://127.0.0.1:43255 create [...]

Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: Get "http://d/v4.5.0/libpod/_ping": dial tcp 127.0.0.1:43255: connect: connection refused

Happens more often in container tasks, but also seen in regular tests.
Example

Probably just needs a check for status=0.
@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. labels Mar 27, 2023
@edsantiago edsantiago mentioned this issue Mar 28, 2023
Closed
@edsantiago
Copy link
Member Author

Still happening: f37 root. Maybe there needs to be a wait-for-socket check?

edsantiago added a commit to edsantiago/libpod that referenced this issue May 9, 2023
@edsantiago
e2e: stop podman.service test: wait for server
ff37615 
Another low-hanging fruit: test flake because podman-remote
trying to contact a server that hadn't come up.

Fixes: containers#17940

Signed-off-by: Ed Santiago <[email protected]>
@edsantiago edsantiago mentioned this issue May 9, 2023
Merged
@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 Aug 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

e2e: stop podman.service test: wait for server edsantiago/libpod
1 participant
@edsantiago