-
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
podman network create/rm: please ignore ENOENT #10926
Comments
Oops, forgot to xref #9041 |
The only place where this error is shown is in ocicni and I already fixed it to make it ignore enoent, at least I thought it was fixed with cri-o/ocicni#85. |
@Luap99 maybe my setup doesn't have that vendored in? Can you reproduce on your system? |
It is vendored in. I just checked the code. CNI does not return a warped error. It uses |
Yes this output looks like it is a logrus.Error. |
Upstream PR containernetworking/cni#850 to fix this is merged. When they release CNI v1.0.0 we can vendor this in (hopefully soon). |
Just a quick comment to reset the nagbot. This is still happening often: Podman network [It] podman network prune
|
Podman network [It] podman network prune
|
CNI version 1.0.0 is available, I can start updating when #11322 is merged. |
Update CNI so we can match wrapped errors. This should silence ENOENT warnings when trying to read the cni conflist files. Fixes containers#10926 Because CNI v1.0.0 contains breaking changes we have to change some import paths. Also we cannot update the CNI version used for the conflist files created by `podman network create` because this would require at least containernetwork-plugins v1.0.1 and a updated dnsname plugin. Because this will take a while until it lands in most distros we should not use this version. So keep using v0.4.0 for now. The update from checkpoint-restore/checkpointctl is also required to make sure it no longer uses CNI to read the network status. [NO TESTS NEEDED] Signed-off-by: Paul Holzinger <[email protected]>
There's a race condition between the time podman reads its CNI directory and the time it tries to read conflist files. Trivial reproducer (requires two shells):
Within less than ten seconds, one or the other will spit out:
...where
xxx
is the name of the other window (e.g. you will see "bbb" in the aaa window and vice-versa).(Note: even though it says ERRO, it's not an error and does not cause a nonzero exit status).
This is really annoying to me when looking at integration-test logs, because they all show up in bright scary orange that makes me think there's an error (and, in some cases, hides real errors because of the cry-wolf thing).
To normal-people users, this is probably kind of alarming, and would presumably cause them to waste an indeterminate amount of time looking into it.
Easy/obvious solution is to just ignore ENOENT, ¿que no?
The text was updated successfully, but these errors were encountered: