-
Notifications
You must be signed in to change notification settings - Fork 260
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
e2e: cloud-config
secret can be removed before CAPO/CAPI resources being deleted
#2110
Comments
I'm totally unsure if we'll actually fix that situation because CAPI framework waits for a cluster to be deleted as we can see here: However it seems like nothing waits for the OpenStackServers to be deleted in my initial implementation. I'll play around that for now. |
/cc @mdbooth |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/kind bug
What steps did you take and what happened:
In e2e, when tearing down the tests, we remove the namespace that was used.
In that namespace, there is the
cloud-config
secret that is used to store the OpenStack credentials.If that secret is removed, some resources will fail to be reconciled by the cluster so deleting the namespace at the end of the tests is problematic if not everything was reconciled.
This could lead to this error:
(Found via #2067)
I think until now we were lucky because all cluster resources were removed before the namespace gets deleted but with the new controller things might take a little bit more time and we found this issue again.
The text was updated successfully, but these errors were encountered: