Share via

AKS Starting issues

Ashok Reddy 21 Reputation points
2021-08-19T07:25:44.753+00:00

After aks stop and starting time we are getting below issue.

Operation failed with status: 'Bad Request'. Details: managed cluster is in Provisioning State(Stopping) and Power State(Stopped), starting cannot be performed

Suggest me on this to resolve the issue.

Azure Kubernetes Service
Azure Kubernetes Service

An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.

0 comments No comments

Answer accepted by question author

shiva patpi 13,396 Reputation points Microsoft Employee Moderator
2021-08-19T14:15:04.337+00:00

Hello @Ashok Reddy ,
It seems cluster was stuck in "Stopping" state. Did you try to STOP and immediately trying to START the cluster ?
Are you still not able to start the cluster yet ?
Can you check the current provisioning state of the AKS cluster from Azure Portal ?
Also check VMSS instances (If the cluster is stopped , you should not see any running instances under VMSS).

Can you check if you are able to run kubectl commands ?
Is this the private cluster ?

If you are still seeing the issue , try to run the below command:
az resource update -n <aks cluster name> -g <rgname> --namespace Microsoft.ContainerService --resource-type ManagedClusters

Regards,
Shiva.

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. HOLDING, Jacob 6 Reputation points
    2021-10-05T09:11:03.463+00:00

    Hi @shiva patpi , I am getting the same error.

    The current state of the cluster in the portal is: Stopping (Stopped)
    VMSS instance shows 0 nodes and succeeded state
    I Cannot run kubectl commands

    running the suggested command gives me:
    Message: An error has occurred in subscription 8a******redacted*****, resourceGroup: ****redacted*****-rg request: Managed Cluster is not running, no operations are allowed.

    our cluster has not been stopped / immediately started we attempted to stop at 22:00 BST yesterday which timed out after an hour and getting the above error this morning when attempting to start

    Was this answer helpful?

    1 person found this answer helpful.

  2. Ashok Reddy 21 Reputation points
    2021-08-20T05:13:12.107+00:00

    Yes, I am starting immediately cluster after stop. After couple of minutes its started as expected.

    Thank You...

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.