This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 57.99999999999999%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
Hello all,
we have a couple of aks cluster running with stop start automation. Since today all clusters failed to start (failed state, Failed (Running)) with the following message:
Failed to start the Kubernetes service 'CLUSTERNAME'.
Error: Reconcile VNet failed.
Details: VNetReconciler retry failed: Category: ClientError; Code: Unspecified; SubCode: InUseSubnetCannotBeUpdated; Message: ; InnerMessage: ; Dependency: Microsoft.Network/virtualNetworks; OrginalError: Code="InUseSubnetCannotBeUpdated" Message="Subnet aks-subnet is in use and cannot be updated." Details=[]; AKSTeam: Networking, Retriable: false.
We didn't change anything and we are not using a custom subnet (default kubenet). Google isn't helpful here either (stackoverflow, github, mailinglist), there no topics which are helpful right now.
Cluster was created with
...
--enable-aad ^
--enable-azure-rbac ^
--disable-local-accounts ^
--load-balancer-sku basic ^
...
The basic sku public ip address shouldn't be a problem until 30 September 2025.
Kubernetes Versions is out of support 1.22.4 is currently beeing used but we can't updated it since the cluster doesn't start
in the first place. I don't think this is the issue though.
Can anyone help here or maybe has the same issue?
Best
Simon
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 98%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hello @Admin OpenKonsequenz , @Nils Gruson , @Liebau, Robert ,
If you are coming across the error message : InUseSubnetCannotBeUpdated , please run below commands:
Refresh the VNET using the command:
az resource update --ids /subscriptions/subId/resourceGroups/MC_resourcegroup/providers/Microsoft.Network/virtualNetworks/vnetname
Refresh the AKS cluster using the command::
az resource update --ids /subscriptions/ subId /resourceGroups/resourcegroupname/providers/Microsoft.ContainerService/managedClusters/aksclustername
regards,
Shiva.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 82%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELR%3C/text%3E%3C/svg%3E)
Hi shivapatpi,
az resource update -n aksclustername -g aksresourcegroup --namespace Microsoft.ContainerService --resource-type ManagedClusters
=> results in cluster is stuck in starting state and node pools are empty
az resource update --ids /subscriptions/subId/resourceGroups/MC_resourcegroup/providers/Microsoft.Network/virtualNetworks/vnetname
=> could be successfully executed
az resource update --ids /subscriptions/ subId /resourceGroups/resourcegroupname/providers/Microsoft.ContainerService/managedClusters/aksclustername
=> could not be executed because of the cluster is stuck in starting state and the node pools are empty
But restarting the Virtual machine scale set solved the stuck in starting state and get the cluster back working.
Thanks for the support...
Hello @Admin OpenKonsequenz ,
Can you try running the below command on your AKS cluster , below command will try to refresh your AKS cluster and restore to last known good state.
az resource update -n aksclustername -g aksresourcegroup --namespace Microsoft.ContainerService --resource-type ManagedClusters
Regards,
Shiva.
I have the same problem since yesterday, I cannot start my AKS cluster anymore.
No changes were recently made to the cluster configuration.
When I try Shiva's suggestion, the command fails after 15 minutes or so.
From the activity log:
Operations are not allowed when the managed cluster is not in the Running power state.
Hello @Nils Gruson - what is the error which you are getting when you try to start the AKS cluster ?
Can you kindly provide more details like if you have any correlationID from the logs ?
FYI - above command works only if the cluster is not in STOPPED state.
Regards,
Shiva.
The correlation id from the Activity Log entry is a3156721-bbc0-4940-86ae-710c0bb747c3.
The error is:
"statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"InternalOperationError\",\"message\":\"Operation failed after exceeding the maximum retry count.\"}]}}",
I can't find anything that points me to the actual problem.
Hello @Nils Gruson ,
If you are still facing the issue while trying to start the AKS cluster, you might have to reach out to Azure Support for detailed troubleshooting & Mitigation.
Right now, I see the cluster is in failed, try to re-run the above command - if that helps!
Regards,
Shiva.
I have the same problem since yesterday and also using start/stop automation to save budget over the night.
We also can't start it manually via aks command or UI
Can you try running the below command on your AKS cluster , below command will try to refresh your AKS cluster and restore to last known good state.
az resource update -n aksclustername -g aksresourcegroup --namespace Microsoft.ContainerService --resource-type ManagedClusters
Thanks Siva for your quick answer.
After running the command I get the same error like ngruson:
(InternalOperationError) Operation failed after exceeding the maximum retry count.
Code: InternalOperationError
Message: Operation failed after exceeding the maximum retry count.