Azure / aksArc

# Welcome to the Azure Kubernetes Service on Azure Stack HCI repo This is where the AKS-HCI team will track features and issues with AKS-HCI. We will monitor this repo in order to engage with our community and discuss questions, customer scenarios, or feature requests. Checkout our projects tab to see the roadmap for AKS-HCI!
MIT License
109 stars 45 forks source link

[BUG] Not able to delete Hybrid AKS clusters. Only node pools gets deleted after that the resource bridge is broken. #342

Closed The-TeQnician closed 1 year ago

The-TeQnician commented 1 year ago

Describe the bug I am not able to delete Hybrid AKS clusters from Azure Stack HCI. If i want to delete a successfully deployed cluster via the portal it only deletes the nodepool workers and then stops. Load balancer and control plane stay behind and after 15 to 30 minutes the delete job fails with an undefined error. After that the resource bridge stops working and new deployments also fail.

To Reproduce Steps to reproduce the behavior:

  1. From the portal go to the Hybrid AKS cluster
  2. Click on delete
  3. Delete jobs runs and nodepools get deleted.
  4. Then the delete jobs keeps on running and fails

Expected behavior When i delete an hybrid AKS cluster from the portal i expect it to work. Node pools, Load Balancer and Management pane deleted from HCI cluster and objects removed from the portal.

Screenshots Inkedportal1 Inkedfailovercluster image

Environment (please complete the following information):

Additional context This environment is a 4 node cluster with Azure Stack HCI 22H2. Environments contains AKS Resource bridge, ARC VM Self Service and Hybrid AKS resource bridges. Even after several redploys of the resource bridge it keeps failing when deleting Hybrid AKS clusters.

HariPrasadV commented 1 year ago

@The-TeQnician we rolled out a fix for the delete issue. One of the resourceTypes: provisionedClusters/upgradeProfiles was under a feature flag and since your subscription was not registered for that feature flag, azure was not able to delete it, and in turn it was blocking the delete of the parent resource (provisionedClusters) as well. We have removed that feature flag and rolled out the change and you should be able to see it as a part of Microsoft.HybridContainerService RP in your subscription now (You can check az provider show -n "Microsoft.HybridContainerService" to see if it has "resourceType": "provisionedClusters/upgradeProfiles") Can you please retry the delete and let us know how it goes?

The-TeQnician commented 1 year ago

Hi @HariPrasadV, i have been testing this and it seems to fixed the issue when the resource type is registered! Great thanks!!