Parses the IP addr passed as CIDR from the delegated IPAM and then use the IP addr from the parsed prefix.

[vipul-21]

Fixes: #22917
Parses the ipaddress passed as CIDR from the delegated Ipam. And then use the ipaddress from the parsed prefix.

---

Fixes: #21421

[christarazi]

@vipul-21 Could you move the "Fixes ..." out from the commit title and into the commit msg itself? This will resolve the checkpatch failure in the CI.

[christarazi]

CI is failing with

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fa6a4caa47ec2fddf932d3a5302381c76201298b36ca73df188a98fcd4b20ad1": unable to prepare IP addressing for ''fd00:10:244:0:1::d616'': netip.ParsePrefix("fd00:10:244:0:1::d616"): no ''/''

now

[vipul-21]

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "fa6a4caa47ec2fddf932d3a5302381c76201298b36ca73df188a98fcd4b20ad1": unable to prepare IP addressing for ''fd00:10:244:0:1::d616'': netip.ParsePrefix("fd00:10:244:0:1::d616"): no ''/''

Is there a way I can run these test locally ?

[christarazi]

I would suggest following https://docs.cilium.io/en/v1.12/gettingstarted/k8s-install-default/ as it seems like a general failure in creating any pod.

[christarazi]

/test

Job 'Cilium-PR-K8s-1.16-kernel-4.9' failed:

Click to show.

Test Name

K8sDatapathConfig MonitorAggregation Checks that monitor aggregation restricts notifications

Failure Output

FAIL: Unable to retrieve all pods to restart unmanaged pods with 'kubectl -n kube-system get pods -o json': Exitcode: -1 

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.16-kernel-4.9 so I can create one.

---

Edit:

• Runtime hit CI: TestArpPingHandlingForMultiDevice gets stuck due to race #22373
• 4.9 hit similar symptoms to CI: K8sUpdates Tests upgrade and downgrade from a Cilium stable image to master #22850 & CI: K8sDatapathConfig MonitorAggregation Checks that monitor aggregation restricts notifications #21175 related to etcdserver: request timed out

[vipul-21]

K8sDatapathConfig

Seems like the issue might be a flaky one. Can we retry this ?
I'll try to replicate the issue locally.

[christarazi]

@vipul-21 No need to reproduce locally. It seems that the CI failures are flakes.

[vipul-21]

@christarazi @nathanjsweet Thanks for the review and approval. Can we merge the PR ?

[joestringer]

I've marked this for backport since it seems to address a regression in 1.13.x in the delegated IPAM area.