cluster-api-provider-azure icon indicating copy to clipboard operation
cluster-api-provider-azure copied to clipboard

Self-Hosted cluster deletion failing in scenarios when manual deletion is attempted first.

Open ardixit-msft-la opened this issue 1 year ago • 9 comments

/kind bug

[Before submitting an issue, have you checked the Troubleshooting Guide?]

What steps did you take and what happened: [A clear and concise description of what the bug is.] In cases where manual deletion of self-hosted cluster is attempted before deleting through kubectl command, the cluster never gets deleted. On reattempting manual deletions, the resources are recreated while the provisioning state of the cluster is shown as deleting. kubectl --kubeconfig C:\Users\ardixit.kube\management get clusters image

What did you expect to happen: After the deletion is attempted through the following command

kubectl --kubeconfig C:\Users\ardixit.kube\management delete cluster flexiblec220849

The cluster should be deleted instead of hanging the deleting state. The cluster should not be recreated.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] This issue was reproduced with an AKS setup with 4 cluster, each having 5 user nodepools. The issue is intermittent and happens twice in approx. 10 runs.

Environment:

  • cluster-api-provider-azure version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

ardixit-msft-la avatar Feb 29 '24 18:02 ardixit-msft-la