-
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
Test flaking with "machine.cluster.x-k8s.io/certificates-expiry" does not exist #8747
Comments
/triage accepted |
Just curious. Can you add a link to the specific job run please? |
I'm hopefully going to do a deep dive on this later on - hopefully not to tough to fix seeing as it's just been introduced Offchance it's SSA 🤔 - which would be more complex, but I'm betting it's a timing issue. |
Thx for the link! |
/assign @adilGhaffarDev |
@killianmuldoon: GitHub didn't allow me to assign the following users: adilGhaffarDev. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
/reopen Until we see some evidence this fixes the flake. |
@killianmuldoon: Reopened 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. |
Fix in #8758 didn't work - looking at this again I think the fail in cluster-api/test/e2e/clusterclass_rollout.go Line 815 in c340c13
@sbueringer - WDYT? |
Change in #8761 seemed to fix this for main, but the solution is to completely ignore the error. I'd like to revisit this to understand how we can handle the error inside the /assign |
@killianmuldoon Can we please rollback the change in #8761? Let's instead pass in Gomega into without and then use g.Fail |
Yeah - something like that is the plan. Let's wait until we have some functioning CI first. |
This test is now green. /close |
@killianmuldoon: 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. |
/reopen This issue has re-emerged in the last few days - https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*&xjob=.*-provider-.*#7b3ebfaf894e9e2e1fe0 |
@killianmuldoon: Reopened 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. |
/close The fix in #8897 has solved this for now. |
@killianmuldoon: 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. |
Which jobs are flaking?
e.g. https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main
Which tests are flaking?
e.g. capi-e2e.[It] When testing ClusterClass rollouts [ClusterClass] Should successfully rollout the managed topology upon changes to the ClusterClass
Since when has it been flaking?
Since merging #8711
Testgrid link
https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main
Reason for failure (if possible)
Probably related to changes in #8711 where the order of putting this annotation in place was changed.
Failed run here: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-e2e-main/1661640513482133504
Anything else we need to know?
No response
Label(s) to be applied
/kind flake
The text was updated successfully, but these errors were encountered: