1

I've got a k8s (on-premise) cluster with 1 master and 3 workers, all ubuntu, latest LTS version.

2 workers are running fine, but pods getting scheduled to one stay in the ContainerCreating state with the error.

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "1234" network for pod "clean-updater-hxknv": networkPlugin cni failed to set up pod "clean-updater-hxknv_default" network: failed to set bridge addr: "cni0" already has an IP address different from 10.244.6.1/24

cni0 has an ip of:

cni0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 inet 10.244.3.1/24 brd 10.244.3.255 scope global cni0

I've tried kubeadm reset and join again on the node but it didnt help. How to fix this error?

Improve this question

1 Answer 1

Reset to default
3

I had this happen to me when my flannel and cni0 inet addresses were out of sync. Bringing down the cni0 bridge made it resync for me:

ifconfig cni0 down
brctl delbr cni0

Or if that doesn't work:

sudo ip link delete cni0 type bridge

Hope that helps.

Improve this answer
2
  • actually had this again on another cluster a few weeks ago. will try soon
    – Serve Laurijssen
    Commented Sep 24, 2022 at 10:44
  • 1
    Second option worked for me, thanks!
    – englishPete
    Commented Oct 5, 2023 at 19:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.