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

stop podman.service: unable to connect to podman socket: dial tcp ECONNREFUSED #16277

Closed
edsantiago opened this issue Oct 24, 2022 · 6 comments
Closed
Labels
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

Been happening for a while, but this is the first time I see it happen without the fd flake:

stop podman.service
...
Execing /var/tmp/go/src/github.com/containers/podman/bin/podman-remote --url tcp://127.0.0.1:38573 create --tty --name top_XVlBzgba --entrypoint top quay.io/libpod/alpine_labels:latest
         
Listening on 127.0.0.1:38573 as 3.
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.3.0/libpod/_ping": dial tcp 127.0.0.1:38573: connect: connection refused

This seems to be a one-off flake: the kind that passes when ginkgo retries. But it seems to have a really odd pattern, a correlation with #15943 (the fd flake): nearly every time we see the fd flake, we see one of these stop podman.service flakes. The difference from the above log excerpt is that when the fd flake happens, instead of ECONNREFUSED, the stop test flakes with:

Error: unexpected fd received from systemd: cannot listen on it

The above excerpt and link are the first time I see stop flaking without the fd flake.

Systemd activate [It] stop podman.service

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Jan 3, 2023

Is this the one that @vrothberg was working on?

@vrothberg
Copy link
Member

Is this the one that @vrothberg was working on?

No. I fixed a flake in the system tests but we're facing an e2e test here, see https://api.cirrus-ci.com/v1/artifact/task/6512229666258944/html/int-podman-ubuntu-2204-rootless-host.log.html#t--stop-podman-service--1.

@vrothberg
Copy link
Member

@edsantiago are we still seeing this flake?

@edsantiago
Copy link
Member Author

No instances since 10-21. Since we no longer test Ubuntu, I'll just close and assume we won't see it again.

@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 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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

3 participants