-
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
Timed out after 180.001s. waiting for cluster deletion timed out #11162
Comments
cc @kubernetes-sigs/cluster-api-release-team |
I took an initial look and the cluster deletion is stuck because MachinePools are stuck in deletion cc @jackfrancis @willie-yao @Jont828 |
@sbueringer thx for triaging |
Given how often this test fails and how long it has been failing, I think we should consider removing machinepools from the affected tests. There's a high chance we are missing other issues in the rest of Cluster API because of this flake. |
I can take a look at this if there are no other more urgent MP-related issues @sbueringer |
I can't prioritize MP issues for MP maintainers. But from a CI stability perspective this one is really important. I think either we can fix it soon, or we have to disable MPs for all affected tests. I just don't want to take the risk for much longer that this flake is hiding other issues. |
Which jobs are flaking?
Which tests are flaking?
Since when has it been flaking?
there were few before, more flakes after 6-9-2024
Testgrid link
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-e2e-release-1-8/1833344003316125696
https://storage.googleapis.com/k8s-triage/index.html?job=.*-cluster-api-.*&xjob=.*-provider-.*%7C.*-operator-.*#8899ccb732f9f0e048cb
Reason for failure (if possible)
MachinePool deletion is stuck
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: