-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
www.podman.io flaking - netavark bug? #17044
Comments
podman.io is hosted on github infra. I think one easy change would be to switch it to something like |
Should do redhat.com before google. |
Yesterday, remote f37 root |
Much as we'd love to eat our dogfood, podman.io is not hosted on reliable infrastructure; redhat.com is. Let's see if this gets rid of CI flakes. Closes: containers#17044 Signed-off-by: Ed Santiago <santiago@redhat.com>
Well, shucks. It's not a podman.io problem |
@containers/netavark-maintainers PTAL. It's possible that this is a network-infrastructure problem in Cirrus or gcloud... but it's also possible that our networking is broken. |
Do you know when this started? I know there was a bug in netavark v1.3 which could cause this. VM image updates should include netavark v1.4 |
Reopening, because #17053 is unlikely to fix anything |
I agree, the common theme here is that it fails with |
@edsantiago New images with a newer netavark were merged last week, does it still happen? |
Sorry for the late reply: we're having a LOT of flakes this week, and I've had to categorize them one by one, which takes time. The last two instances of this flake were on January 16, both on a PR that did not include #16525 (the update-images PR). I feel comfortable closing. Thank you! |
Tests trying to fetch from
www.podman.io
are flaking. Sometimes acurl
timeout, sometimes a DNS name resolution failure:I can't tell if it's a real problem with
podman.io
and/or its nameservers, or a connectivity hiccup, or if it's a Neta/Aardvark problem. The latter seems unlikely because I've only seen this withpodman.io
.There are many more but I'm getting tired of scanning through flake logs.
The text was updated successfully, but these errors were encountered: