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

kubectl delete cluster <cluster_name> wont proceed untill we manually delete the IBMPowerVSImage #1690

Closed
Karthik-K-N opened this issue Mar 27, 2024 · 0 comments · Fixed by #1692
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@Karthik-K-N
Copy link
Contributor

/kind bug
/area provider/ibmcloud

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

Create cluster which auto creates required resources, later try to delete the cluster using kubectl delete cluster <cluster_name>. The cluster deletion wont proceed as the delete call on IBMpowerVSImage is never called, We could see following error in logs

Cluster still has descendants - need to requeue

As a workaround we need to manually delete the IBMPowerVSImage.

This is introduced after adding the PR #1682

What did you expect to happen:

Successfully delete the cluster

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api version:
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Mar 27, 2024
@mkumatag mkumatag added this to the v0.8 milestone Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants