Skip to content
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

Closed
killianmuldoon opened this issue May 25, 2023 · 19 comments · Fixed by #8758
Closed
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@killianmuldoon
Copy link
Contributor

killianmuldoon commented May 25, 2023

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

@k8s-ci-robot k8s-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 25, 2023
@killianmuldoon
Copy link
Contributor Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 25, 2023
@sbueringer
Copy link
Member

sbueringer commented May 25, 2023

Just curious. Can you add a link to the specific job run please?

@killianmuldoon
Copy link
Contributor Author

@killianmuldoon
Copy link
Contributor Author

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.

@sbueringer
Copy link
Member

Thx for the link!

@killianmuldoon
Copy link
Contributor Author

/assign @adilGhaffarDev

@k8s-ci-robot
Copy link
Contributor

@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.
For more information please see the contributor guide

In response to this:

/assign @adilGhaffarDev

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.

@killianmuldoon
Copy link
Contributor Author

/reopen

Until we see some evidence this fixes the flake.

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Reopened this issue.

In response to this:

/reopen

Until we see some evidence this fixes the flake.

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.

@k8s-ci-robot k8s-ci-robot reopened this May 26, 2023
@killianmuldoon
Copy link
Contributor Author

Fix in #8758 didn't work - looking at this again I think the fail in

Fail(fmt.Sprintf("key %q does not exist in map %s", key, m))
needs to be more tolerant instead of directly failing if this annotation isn't available yet.

@sbueringer - WDYT?

@killianmuldoon
Copy link
Contributor Author

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 Eventually call instead of not handling it.

/assign

@sbueringer
Copy link
Member

@killianmuldoon Can we please rollback the change in #8761? Let's instead pass in Gomega into without and then use g.Fail

@killianmuldoon
Copy link
Contributor Author

@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.

@killianmuldoon
Copy link
Contributor Author

This test is now green.

/close

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Closing this issue.

In response to this:

This test is now green.

/close

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.

@killianmuldoon
Copy link
Contributor Author

/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

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Reopened this issue.

In response to this:

/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

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.

@killianmuldoon
Copy link
Contributor Author

/close

The fix in #8897 has solved this for now.

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Closing this issue.

In response to this:

/close

The fix in #8897 has solved this for now.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants