Deleted clusters don't seem to actually get deleted

[blackbaud-brandonstirnaman]

While attempting to get a working cluster during the capacity issues I had been creating/deleting a few clusters with similar names. I was unable to delete AKS instances within the portal (or CLI) but I could delete the Resource Group the AKS instance was in and it would clean up any trace of the cluster in the portal after a few minutes.

Today, I get an error if I try to create a new cluster (now days later) using one of the names I had used/deleted a few days ago. I'm guessing resources aren't getting cleaned up in the master control plane? I have no cluster with this name/RG according to the portal atm but I get this error when running az aks create.

Operation failed with status: 'Conflict'. Details: Operation is not allowed: Cluster in a failed state

[davidjsanders]

This could be related to my issue #15 as I have to manually delete the primary group a second time after the portal/cli says it's been deleted - it magically reappears :)

David

[slack]

There are a few fixes around delete and name re-use. Will update this issue when they are shipped.

Related #38

[sgoings]

@blackbaud-brandonstirnaman we've pushed a bunch of changes to prod around making deletes more robust so I believe this is now resolved. I also see related issues as being resolved (#51). Closing, but if you're still seeing this issue feel free to reopen!