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
{"level":"error","ts":"2023-11-02T23:00:02.818Z","caller":"routed-eni-cni-plugin/cni.go:126","msg":"Failed SetupPodNetwork for container ********:
SetupPodNetwork:
failed to setup veth pair: failed to setup veth network: setup NS network:
failed to add default gateway: one of Dst.IP, Src, or Gw must not be nil"}
Attach logs
What you expected to happen:
Check non-nil err or device -1 or nil IP here -
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
What happened:
When IP address is not available in IPAMD we see the below error in logs -
And we return non-nil error -
amazon-vpc-cni-k8s/pkg/ipamd/rpc_handler.go
Line 152 in d49c8a3
When ANNOTATE_POD_IP is not configured then we just return non-nil and CNI will fail add.
But when ANNOTATE_POD_IP is configured -
amazon-vpc-cni-k8s/pkg/ipamd/rpc_handler.go
Lines 182 to 202 in d49c8a3
We end up overwriting the "err" hence we would see this log with err overwritten with "nil" -
Hence we will not land here - https://github.com/aws/amazon-vpc-cni-k8s/blob/master/cmd/routed-eni-cni-plugin/cni.go#L178-L182
Leading to setupPodNetwork with nil IP.
Attach logs
What you expected to happen:
Check non-nil err or device -1 or nil IP here -
amazon-vpc-cni-k8s/pkg/ipamd/rpc_handler.go
Line 182 in d49c8a3
How to reproduce it (as minimally and precisely as possible):
Exhaust IP and have ANNOTATE_POD_IP set
Anything else we need to know?: N/A
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: