-
Notifications
You must be signed in to change notification settings - Fork 59
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
PODs stuck in error "Failed to create pod sandbox" #452
Comments
yes same issue for me, looks like kubeovn and cilium has a small war there
|
by the way I am using Cozystack 0.17.1 |
Hey! Please provide more details for debug.
|
my settings are below
k8s node ips
2 weeks ago I installed 0.16.2 with similar setup and it was ok |
I have the same issue while installing cozystack 1.7.1. |
my patch.yaml
my patch-controlplane.yaml
node ip's |
Could you check why kube-ovn-cni pods are in crashloopback? Check the logs and events |
It seems this is related to issue #449, which was fixed in v0.17.1. Unfortunately, we didn't update the cozystack-installer.yaml manifests, so you're probably still running v0.17.0. The manifest was updated in #453 (merged this morning). Please try this version, and if it doesn’t work, feel free to reopen the issue. |
Hi! I'm trying to install cozystack and after running this command
kubectl apply -f https://github.com/aenix-io/cozystack/raw/v0.17.1/manifests/cozystack-installer.yaml
some pods stuck in error
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "<...>": plugin type="kube-ovn" failed (add): RPC failed; Post "http://dummy/api/v1/add": dial unix /run/openvswitch/kube-ovn-daemon.sock: connect: no such file or directory
kube-ovn-cni pods in Back-off restarting with error
Liveness probe failed: dial tcp <node ip>:10665: connect: connection refused
The text was updated successfully, but these errors were encountered: