-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster API quick-start with dualstack is flaky #8816
Comments
/triage accepted |
/help |
@killianmuldoon: GuidelinesPlease ensure that the issue body includes answers to the following questions:
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 In response to this:
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/test-infra repository. |
/assign @nawazkh |
This has been fixed with #9252 and the CI signal for capi-e2e-dualstack-and-ipv6-main looks green. Shall we close out this issue? |
Currently, in dual-stack I only see this flake: with this error:
This is a kubetest that is failing here: Not really sure what could be the root cause of this, few things that I think we can check:
We need to either update this issue or create a new one for "conformance tests" flake because I believe this issue is tracking a different flake that is not happening anymore. @killianmuldoon please confirm. |
Maybe we could collect the logs from the conformance container when hitting the issue to further diagnoes this. More persistent link: https://storage.googleapis.com/k8s-triage/index.html?date=2023-11-13&job=.*-cluster-api-e2e-dualstack-.*&xjob=.*-provider-.*#3ad7d5d4d855de76fe3b |
I would also like to add there are 2 other flakes in dual stack, they happen very rarely:
Conformance flake is the one that happens most of the time. |
Not working this actively, so unassuming myself now. But please feel free to pull me in @adilGhaffarDev when debugging |
/assign |
We are already collecting them. This error is for ipv4 primary
In the case of ipv6 primary
|
@killianmuldoon it seems that flaky dualstack tests are general and not related to MachinePools? Ref: @willie-yao is tracking restoring those tests as part of graduating MachinePool from experimental. What should the path forward be for MachinePools + dualstack tests given all of this context? |
I think the MachinePool versions of these tests are much flakier than the current test. I think we should figure out the issues in the MachinePool PR while continuing to try to triage and fix this separate underlying flake. |
/priority important-soon |
This seems to be good since #10424 merged 🎉 /close |
@chrischdi: Closing this issue. In response to this:
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/test-infra repository. |
Great work on fixing this! |
Yikes, fun one :) @willie-yao you should be able to re-introduce MachinePools into tests and we'll be able to confirm right away that there's no MachinePool regression here. |
Good catch! |
Note: This got cherry-picked back to v1.5, v1.6 and v1.7. |
Which jobs are flaking?
capi-e2e-dualstack-and-ipv6-main
Which tests are flaking?
Failing test cases:
Since when has it been flaking?
Since the dualstack tests were merged.
Testgrid link
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-dualstack-and-ipv6-main
Reason for failure (if possible)
Not clear at this point but there are some facts we can use to begin debugging this:
should create a single stack service with cluster ip from primary service range
test. The error message is:service dualstack-6332/defaultclusterip expected family IPv4 at index[0] got IPv6
orservice dualstack-5879/defaultclusterip expected family IPv6 at index[0] got IPv4
depending on the test variant.Anything else we need to know?
No response
Label(s) to be applied
/kind flake
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: