Failing e2e tests due to networking conformance test

[cprivitere]

Which jobs are failing?

• periodic-cluster-api-e2e-main
• periodic-cluster-api-e2e-mink8s-main
• periodic-cluster-api-e2e-latestk8s-main
• periodic-cluster-api-e2e-release-1-9
• periodic-cluster-api-e2e-mink8s-release-1-8
• periodic-cluster-api-e2e-mink8s-release-1-9
• periodic-cluster-api-e2e-mink8s-release-1-10

Which tests are failing?

• Kubernetes e2e suite [It] [sig-network] [Feature:IPv6DualStack] Granular Checks: Services Secondary IP Family [LinuxOnly] should function for service endpoints using hostNetwork
• capi-e2e [It] When following the Cluster API quick-start with dualstack and ipv4 primary [IPv6] Should create a workload cluster
• capi-e2e [It] When following the Cluster API quick-start with dualstack and ipv4 primary [IPv6] Should create a workload cluster [IPv6]

Since when has it been failing?

07/03

Testgrid link

https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*e2e.*&xjob=.*-provider-.*%7C.*-operator-#be8a2f23a346e4a59a6c

Reason for failure (if possible)

Seems like the main error is that the conformance tests are failing due to an issue in the networking test. The stated error on that test is:
[FAILED] failed dialing endpoint, did not find expected responses...

Obviously this needs more investigation to see what the actual problem is.

Anything else we need to know?

• https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*e2e.*&xjob=.*-provider-.*%7C.*-operator-#be8a2f23a346e4a59a6c
• https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*e2e.*&xjob=.*-provider-.*%7C.*-operator-#cc28c16a50d9dcc9866d

Label(s) to be applied

/kind failing-test
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[sbueringer]

/triage accepted

[mboersma]

Since this appeared suddenly on multiple release branches, it could be a change in the e2e environment.

[sbueringer]

That would be my guess as well. Especially since we haven't made a change to release-1.8 in a long time

[sbueringer]

/help

[k8s-ci-robot]

@sbueringer:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mboersma]

See discussion at https://kubernetes.slack.com/archives/C7J9RP96G/p1751991861631429

[adilGhaffarDev]

/assign
I've run the test multiple times locally (7–8 times), and it's not reproducible. On the test grid, it's always failing.
As discussed on Slack, it's most likely infrastructure-related.

The next step is to move one CAPI job to GKE and monitor it. I'll check with the infra team on Slack to confirm if that's okay.