/test

/test

I checked the CI results from yesterday and found some tests related to PodToService failing. When I re-checked locally, all look good. So, rebased and pushed. @gentoo-root Can you re-trigger the CI again if you have time?

/test

@gentoo-root Sorry to mention you. But, any ideas on failing tests? I tested thoroughly in local and all look good, but in CI they fail.

But, any ideas on failing tests?

None so far, I'd have to investigate. PodToWorld tests fail in the CI due to lack of IPv6 connectivity to the external world in GitHub Actions, and I'm trying to work around it, but in your case the reason must be something else.

None so far, I'd have to investigate. PodToWorld tests fail in the CI due to lack of IPv6 connectivity to the external world in GitHub Actions, and I'm trying to work around it, but in your case the reason must be something else.

I think that according to this error, we need to modify the cilium install defaults in workflow files to include ipv6. https://github.com/cilium/cilium/actions/runs/13328191435/workflow#L138-L156

In the above error, there is no IP for IPv6, resulting in http://:8080.

What do you think?

I think that according to this error, we need to modify the cilium install defaults in workflow files to include ipv6. https://github.com/cilium/cilium/actions/runs/13328191435/workflow#L138-L156

Note that some workflows (e.g. GKE) cannot support IPv6 for technical reasons - thus we cannot simply change the install defaults to force IPv6, it just wouldn't work on setups like GKE.

Thus test code must always dynamically query if IPv6 (or IPv4 for that matter) is actually enabled by Cilium.

I think that according to this error, we need to modify the cilium install defaults in workflow files to include ipv6. https://github.com/cilium/cilium/actions/runs/13328191435/workflow#L138-L156

Note that some workflows (e.g. GKE) cannot support IPv6 for technical reasons - thus we cannot simply change the install defaults to force IPv6, it just wouldn't work on setups like GKE.

Thus test code must always dynamically query if IPv6 (or IPv4 for that matter) is actually enabled by Cilium.

Thank you for clarification.

/test

Conformance Clustermesh, one of the few dual-stack enabled workflows, was green on the first try: https://github.com/cilium/cilium/actions/runs/13534875974

Some of the upgrade tests failed, but that was because of a broken v1.17 CI image, unrelated to this branch. I've restarted the affected workflows.