Skip to content
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

Cillium CNI in VM Drivers fails "address family not supported by protocol"" #18851

Open
medyagh opened this issue May 10, 2024 · 1 comment
Open
Labels
area/cni CNI support help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@medyagh
Copy link
Member

medyagh commented May 10, 2024

          for ISO (qemu driver) I get this error in the pod logs

"failed while reinitializing datapath: listing routing rules: address family not supported by protocol"

fixAndUpdateCiliumCNI ✓
$ kc get pods -A
NAMESPACE     NAME                               READY   STATUS             RESTARTS      AGE
kube-system   cilium-cssbc                       0/1     CrashLoopBackOff   7 (99s ago)   13m
kube-system   cilium-operator-64664858c8-xbs79   1/1     Running            0             13m
kube-system   coredns-7db6d8ff4d-xvrmk           0/1     Pending            0             13m
kube-system   etcd-minikube                      1/1     Running            0             13m
kube-system   kube-apiserver-minikube            1/1     Running            0             13m
kube-system   kube-controller-manager-minikube   1/1     Running            0             13m
kube-system   kube-proxy-d96m9                   1/1     Running            0             13m
kube-system   kube-scheduler-minikube            1/1     Running            0             13m
kube-system   storage-provisioner                0/1     Pending            0             13m

the log for container

$ kc logs cilium-cssbc -n kube-system | grep error
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), install-cni-binaries (init)
time="2024-05-09T23:45:53Z" level=info msg="  --kvstore-max-consecutive-quorum-errors='2'" subsys=daemon
time="2024-05-09T23:45:54Z" level=error msg="Start hook failed" error="daemon creation failed: error while initializing daemon: failed while reinitializing datapath: listing routing rules: address family not supported by protocol" function="cmd.newDaemonPromise.func1 (cmd/daemon_main.go:1686)" subsys=hive
time="2024-05-09T23:45:54Z" level=error msg="Observer job stopped with an error" error="context canceled" func="auth.(*authMapGarbageCollector).handleIdentityChange" name="auth gc-identity-events" subsys=auth
time="2024-05-09T23:45:54Z" level=error msg="Observer job stopped with an error" error="context canceled" func="auth.(*AuthManager).handleAuthRequest" name="auth request-authentication" subsys=auth
time="2024-05-09T23:45:54Z" lev

but it could be only for ISO cilium/cilium#29965

Originally posted by @medyagh in #18846 (comment)

@medyagh medyagh added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 10, 2024
@afbjorklund afbjorklund added the area/cni CNI support label May 10, 2024
@spowelljr
Copy link
Member

Believe this is a dup of #31944 (Cilium pods fail to start after upgrade from 1.15.3 to 1.15.4), and will be fixed with the next v1.15 patch release.

cilium/cilium#32448 (comment)

I think I'll bump the version down to 1.15.3 in my PR #18846 and that should resolve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cni CNI support help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants