AKS stuck on "stopping"

Question

My AKS service (and corresponding nodepool) have got stuck in a provisioningState of "stopping." and can't be restarted. It threw this error but has been stuck for an hour or so.

(ProvisioningControlPlaneError) AKS encountered an internal error while attempting the requested None operation. AKS will continuously retry the requested operation until successful or a retry timeout is hit. Check back to see if the operation requires resubmission. Correlation ID: a847a6ee-869a-4ccf-8fc3-7a850aca14e5, Operation ID: 39f6470e-70bf-44d7-9f27-e2ed0daf435d, Timestamp: 2022-02-10T13:56:29Z.
The operation failed

I've stopped and started it quite happily many times before so seem to have run into an odd error.

Answer 1

Hello, @sjpbb !

While there is a lot of resiliency built into Azure Kubernetes Service (AKS) there are several possible reasons the service might temporarily hang like this.

What should I do if my AKS resource is stuck in a "Stopping" provisioning state?
There are several dependencies that AKS could be waiting for (a connection could be hung, it could be waiting on ACR, etc.) but in general you shouldn't have to wait more than 15 or 20 minutes for this to resolve.

• Look at the AKS troubleshooting documentation to see if you are encountering a common issue.
• If your AKS resource is stuck in a provisioning state for more than 20 minutes, consider opening a support ticket to resolve the issue.
• Check your Kubernetes logs (or other Azure Monitor resources) to better understand the cause of the issue.

Answer 2

OK so after an hour it went to failed and after another hour it restarted (itself?), so we're back and running.