-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Comments
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
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. |
@edsantiago are we still seeing this flake? |
No instances since 10-21. Since we no longer test Ubuntu, I'll just close and assume we won't see it again. |
Been happening for a while, but this is the first time I see it happen without the
fd
flake: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 thefd
flake, we see one of thesestop podman.service
flakes. The difference from the above log excerpt is that when thefd
flake happens, instead of ECONNREFUSED, thestop
test flakes with:The above excerpt and link are the first time I see
stop
flaking without thefd
flake.Systemd activate [It] stop podman.service
The text was updated successfully, but these errors were encountered: