You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have sriov-e1c cluster network and 2 pods are using that CNI.
1st Pod : { "clusterNetwork": "sriov-e1c", "ip6": "2001:4000:aa:34::1" }
2nd Pod : { "clusterNetwork": "sriov-e1c", "ip6": "dynamic" }
But when we deploy pods one pod is in container creating state , and when pod is described below error is observed.
Warning FailedCreatePodSandBox 8s kubelet, controller-0 Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "97ea28cbc67e32a3ec4dede02c39da965659ccc68c62e79649092f884975eff3": CNI network could not be set up: CNI operation for network:sriov-e1c failed with:IP address reservation failed for network:sriov-e1c with error:failed to allocate IP address for network:sriov-e1c with error:static IP allocation failed, requested IP address:2001:4000:aa:34::1 is already in use
What you expected to happen:
Both pods should be up and running
How to reproduce it:
Deploy 2 pods with cluster network as shown above. One pod will not come up.
This occurs sometimes
Anything else we need to know?:
Danm cleaner pods are running in the setup
kubectl get pods -A | grep -i danm-cleaner
kube-system danm-cleaner-5dtgr 1/1 Running 0 99m
Environment:
DANM version (use danm -version):
/usr/libexec/cni/danm --version
2021/11/24 05:33:55 DANM binary was built from release: v4.2.1
2021/11/24 05:33:55 DANM binary was built from commit: abd3c48d_dirty
uname -a
Linux controller-0 3.10.0-1160.15.2.rt56.1152.el7.tis.4.x86_64 #1 SMP PREEMPT RT Wed Jun 9 20:40:45 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Others:
The text was updated successfully, but these errors were encountered:
nknkgithub
changed the title
"Static IP allocation failed", requested IP address already in use issue
"Static IP allocation failed", requested IP address already in use
Nov 24, 2021
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment:
danm -version
):kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: