-
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
flaking test: Machines should remain the same after the upgrade #8101
Comments
Thanks for opening this @aniruddha2000! /triage accepted |
Root cause will be fixed via: #8124 Let's keep this issue until we can verify that the e2e test on main has been stable for a while. |
Issue should be fixed for KCP We have a similar issue with the Cluster topology controller (only affects v1.2 => main and v1.3 => main). Working on this now. For now disabling the rollout check to get back to green CI: #8138 |
@aniruddha2000 @furkatgofurov7 I think we can close this issue given that "Machines should remain the same after the upgrade" doesn't occur anymore. I think I would treat other flakes as a new issue. |
Agree, thanks a lot for all hard work @sbueringer /close |
@furkatgofurov7: 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. |
Failure cluster 6c739992d36a8dc546c4
Error text:
Recent failures:
13/2/2023, 6:30:02 pm periodic-cluster-api-e2e-mink8s-main
13/2/2023, 6:28:53 am periodic-cluster-api-e2e-mink8s-main
13/2/2023, 4:27:50 am periodic-cluster-api-e2e-mink8s-main
12/2/2023, 10:27:52 pm periodic-cluster-api-e2e-mink8s-main
12/2/2023, 8:27:04 pm periodic-cluster-api-e2e-mink8s-main
/kind failing-test
cc @kubernetes-sigs/cluster-api-release-team
The text was updated successfully, but these errors were encountered: