-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Failed to destroy the network because of empty cached cni result. #1055
Labels
Comments
Oops! That's not good! Delete needs to be extremely robust to failure. We clearly need to fix this. |
I'll be happy to contribute a fix. IMHO there are a few options, some of them were mentioned in #1066 discussions too.
Thanks! |
Discussed during community meeting. The decision was 2nd option, "try to delete the network with empty cachedResult as the best effort". PR #1072. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently we met an issue. When the containerd is adding the networks for pods, but at that time, the system is rebooted. It will leave some empty files under /var/lib/cni/results. And after the system is up again, but the pods are deleted by the users. containerd will try to read the cached result to destroy the networks. It will fail directly.
For the cached file, the data will be put in the prevResult field. It seems that a lot of plugins only care about the previous result of the other plugins chained together. And it doesn't care about the previous result of itself.
Can we delay reporting the error of cached result and try to delete the network with cachedResult=nil ?
The text was updated successfully, but these errors were encountered: