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

[v0.10.6] OpenStackCluster stuck on deletion when failing to resolve bastion image #2266

Open
lentzi90 opened this issue Nov 21, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@lentzi90
Copy link
Contributor

/kind bug

What steps did you take and what happened:

  1. Create a cluster
  2. Make sure bastion is enabled and using an image that doesn't exist OR a filter that selects multiple images
  3. Delete the cluster
  4. The cluster stays deleting forever. The OpenStackCluster cannot be deleted because CAPO cannot resolve the bastion image.

Code:

// Attempt to resolve bastion resources before delete. We don't need to worry about starting if the resources have changed on update.
if _, err := resolveBastionResources(scope, clusterResourceName, openStackCluster); err != nil {
return reconcile.Result{}, err
}

What did you expect to happen:

Anything else you would like to add:

This issue is not present in v0.11.

Environment:

  • Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): v0.10.6
  • Cluster-API version:
  • OpenStack version:
  • Minikube/KIND version:
  • Kubernetes version (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Status: Inbox
Development

No branches or pull requests

2 participants