Not possible to create aks cluster #38

aumanjoa · 2017-11-11T21:52:00Z

hi,

I get the following issue when I try to deploy an aks cluster:

Deployment failed. Correlation ID: 08bb265b-1c7c-4c23-8f88-01137f803d8e. Timeout while polling for control plane provisioning status

I have run this commands:

az group create --name chronas-k8s --location westus2

az aks create --resource-group chronas-k8s --name myK8sCluster --agent-count 1 --generate-ssh-keys

The text was updated successfully, but these errors were encountered:

seanmck · 2017-11-12T02:30:55Z

We are currently experiencing an outage in westus2:

https://github.com/Azure/AKS/blob/master/annoucements/service_outage_2017-11-09.md

sauryadas · 2017-11-13T18:08:24Z

@aumanjoa We rolled out AKS in east us. Please deploy in east us.

tmcgannon · 2017-11-13T23:47:05Z

Using same create script as aumanjoa, received the same error in EastUS:

Deployment failed. Correlation ID: 3527dc50-94a6-427b-a7ec-420230ebc986. Timeout while polling for control planeprovisioning status

sauryadas · 2017-11-14T00:18:48Z

@tmcgannon Can you please re try? we were trying to look into the cluster but it looks like you have deleted the cluster. If it fails this time , please leave the cluster as is for us to investigate

tmcgannon · 2017-11-14T00:21:37Z

Failed again. Message:

Deployment failed. Correlation ID: 75c1214d-a8df-4a26-9ece-f71ab318473f. Timeout while polling for control plane provisioning status

aleksen · 2017-11-14T13:03:11Z

I am currently getting similar errors when deploying to ukwest:

    "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceDeploymentFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"ControlPlaneProvisioningInternalError\",\"message\":\"Timeout while polling for control plane provisioning status\"}]}}",

Provisioning in US East works. 👍

Guillaume-Mayer · 2017-11-14T19:52:48Z

Same problem in East US:
az aks create -g aks -n k8s -k 1.8.1 -c 2
Deployment failed. Correlation ID: e3975927-098f-476d-ae7e-37d422a776ec. Timeout while polling for control plane provisioning status

sauryadas · 2017-11-14T19:54:15Z

@Guillaume-Mayer Can you please confirm you have not deleted this cluster, so we can take a look at it?

Guillaume-Mayer · 2017-11-14T19:55:13Z

@sauryadas I confirm, it's still there, but empty

slack · 2017-11-14T22:28:35Z

We are tracking an internal bug that happens if you recreate a cluster in a region with the same cluster name and resource group.

Guillaume-Mayer · 2017-11-17T14:03:04Z

It happened again, with a new name:
az aks create -g aks -n kbn -u gmayer -k 1.8.1 -c 3
Deployment failed. Correlation ID: e39b5d6a-e09a-4258-9657-5408dbb81ad5. Timeout while polling for control plane provisioning status

bialad · 2017-11-17T22:00:05Z

I just had the same issue while creating a new cluster in westeurope with the same name as an old (deleted) cluster in westuk.

az aks create --resource-group=zeptio-aks --name=aks --node-count=1 --node-vm-size=Standard_D1_v2 --dns-name-prefix=zeptio --ssh-key-value=key.pub --kubernetes-version=1.8.1 --generate-ssh-keys

Cluster is still there, do you need it for debugging or shall I delete it?

pjbgf · 2017-11-18T13:01:55Z

Is this related to trying to go for version > 1.8.1? I got the same here as soon as I started setting a version different than the default (1.7.9).

frederimandin · 2017-11-21T11:00:00Z

I had the same issue this morning in westeurope, it seems to work fine with the same command in eastus.

devonbarrett · 2017-11-21T11:35:04Z

Exact same experience. Looks like the same issue is impacting others in #53 and #51

bytesofdhiren · 2017-11-22T08:10:00Z

Looks like it's working in East US region.
Also, I found that there was some wrong value in --node-vm-size parameter.

The issue is, az throws same error message even if there is something wrong with the command.

azzlack · 2017-11-22T09:37:50Z

Worked for me just now.
Used the command az aks create --resource-group Hub --name bkhub-cluster --node-count 1 --node-vm-size Standard_D1_v2 --dns-name-prefix bkhub --kubernetes-version=1.8.1 --generate-ssh-keys

argoneus · 2017-12-19T16:29:51Z

I first created the resource group:
az group create --name test-k8s-group -l eastus

Then attempted to create a cluster using:
az aks create --resource-group test-k8s-group --name test-k8s --node-count 1 --generate-ssh-keys

I'm receiving this error in eastus on creating an AKS cluster:
Deployment failed. Correlation ID: 65146199-2d9f-4cdf-9e8c-4380acb72825. Timeout while polling for control plane provisioning status

I deleted the cluster and resource group, and attempted to re-deploy, and am now receiving the error:
Operation failed with status: 'Conflict'. Details: Operation is not allowed: Another operation is in progress

slack · 2017-12-19T22:00:22Z

@argoneus we had an issue with one of the provisioning controllers in East US this morning. You should be able to create a new cluster (with a different name).

I'm going to close out this issue for the time being.

xszaboj · 2018-02-15T09:46:38Z

Hi,

I'm not able to create new AKS cluster in westeurope

I first set my subscription:
az account set --subscription MYSUBSCRIBTION

After that created new resource group:
az group create --name iatest-aks-group --location westeurope

And tried to create new AKS cluster:
az aks create --resource-group iatest-aks-group --name iatest-aks-cluster --node-count 3 --generate-ssh-keys --service-principal **** --client-secret ****

First it failed with:

Deployment failed. Correlation ID: ae964943-d868-471d-9d2f-8608182855e3. Azure Container Service is unable to provision an AKS cluster in westeurope, due to an operational threshold. Please try again later or use an alternate location. For more details please refer to: https://github.com/Azure/AKS/blob/master/preview_regions.md

So I waited for an hour or so and tried again the same command. And it started running, but it eventually failed with:

Deployment failed. Correlation ID: 4177d83e-5819-4257-8d97-fb174291fa57. Timeout while polling for control plane provisioning status

Any suggestion how to approach this? Should I wait bit more, or am I doing something wrong?

Thanks

alexanderknapstein · 2018-03-09T13:55:38Z

Hi,

I'm not able to create new AKS cluster in westeurope:

az group create --name ilKubernetesGroup01 --location westeurope
az aks create --resource-group ilKubernetesGroup01 --name ilKube01 --node-count 1 --generate-ssh-keys

Failed with:

Deployment failed. Correlation ID: f253419f-65b5-48b8-8cf9-32be75b545da. Timeout while polling for control plane provisioning status

az aks list shows:

[...] "location": "westeurope",
"name": "ilKube01",
"provisioningState": "Failed",
"resourceGroup": "ilKubernetesGroup01",
"servicePrincipalProfile": {
"additionalProperties": {}, [...]

evanlouie · 2018-03-14T19:28:59Z

@sauryadas just got this error today while trying to provision in canadacentral:
Deployment failed. Correlation ID: a470bd38-07c4-4b9b-93f8-aac634377ed5. failed to RpGetControlPlane

cc: @brusMX

sauryadas · 2018-03-14T19:32:02Z

apologies ... we are working on a fix and should be up soon

SarahU · 2018-03-19T16:55:40Z

Similar problem trying to change Node pool count in West Europe: Error: PutControlPlane error

jay-wilson · 2018-03-21T06:50:27Z

Faced a similar issue at canada central for the past week. Resource group was created but the aks creation is failing. Now neither able to delete the hung aks cluster nor the resource group

    Name               Location       ResourceGroup        KubernetesVersion    ProvisioningState 
    JayPgDbReplicaSet  canadacentral  JayPgResourceGroup   1.8.7                Failed
    AKS-Jay-20Mar-PG   canadacentral  RG_Jay_20Mar_PG      1.8.7                Failed
    JayPgDbReplicaSet  canadacentral  RG_Jay_20Mar_PG      1.8.7                Failed

Upon trying to delete the cluster, it takes a long time and eventually fails

az aks delete -n JayPgDbReplicaSet -g JayPgResourceGroup
Deployment failed. Correlation ID: 2d6eb236-a939-4dda-a921-db0b0c43c56f. operationWrapper.Status: 'Accepted' does not represent a terminating state. Error: null

dmitrytokarev · 2018-04-18T09:33:42Z

keep getting this error on k8s version 1.9.2 on westus2 region (k8s ver 1.7.* deployed OK):

Python 3.6.3
azure-cli==2.0.31
az aks create --resource-group ***** --name ***** --node-count 1 --generate-ssh-keys -k 1.9.2

Deployment failed. Correlation ID: 2cfb22c5-a111-4e40-83d7-60e79f231da0. PutControlPlane error

adamkruszewski · 2018-04-19T12:30:10Z

Got the same problem "PutControlPlane error", it seems it happens always, doesn't matter what ResourceGroup name, cluster name or location I choose (I have tried westeurope, centralus, eastus so far).

az aks create \ 
       --resource-group    kubeRG \
       --name              kubeCluster4 \
       --node-count        1 \
       --dns-name-prefix   kubeCl \
       --generate-ssh-keys

kwal · 2018-04-19T14:28:51Z

Experiencing the same issue as @adamkruszewski - can't create clusters in any region at the moment.

dad045 · 2018-04-19T15:13:43Z

@kwal
I was having the same problem... but when I specified the version it worked for me

--kubernetes-version 1.9.2

full command used:

az aks create -g GroupName -n ClusterName --node-count 3 --node-vm-size Standard_D4s_v3 --generate-ssh-keys --location eastus --kubernetes-version 1.9.2

sauryadas closed this as completed Nov 13, 2017

sauryadas reopened this Nov 13, 2017

slack added bug known-issue labels Nov 14, 2017

slack mentioned this issue Nov 14, 2017

Deleted clusters don't seem to actually get deleted #33

Closed

slack closed this as completed Dec 19, 2017

c-w mentioned this issue Apr 19, 2018

Fix command to create AKS cluster MicrosoftDocs/azure-docs#7442

Closed

rverschuur mentioned this issue Sep 18, 2019

Capacity errors returned on AKS create in WestEurope #1214

Closed

ghost locked as resolved and limited conversation to collaborators Aug 13, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Not possible to create aks cluster #38

Not possible to create aks cluster #38

aumanjoa commented Nov 11, 2017

seanmck commented Nov 12, 2017

sauryadas commented Nov 13, 2017

tmcgannon commented Nov 13, 2017

sauryadas commented Nov 14, 2017

tmcgannon commented Nov 14, 2017

aleksen commented Nov 14, 2017

Guillaume-Mayer commented Nov 14, 2017

sauryadas commented Nov 14, 2017

Guillaume-Mayer commented Nov 14, 2017 •

edited

Loading

slack commented Nov 14, 2017

Guillaume-Mayer commented Nov 17, 2017

bialad commented Nov 17, 2017

pjbgf commented Nov 18, 2017

frederimandin commented Nov 21, 2017

devonbarrett commented Nov 21, 2017

bytesofdhiren commented Nov 22, 2017

azzlack commented Nov 22, 2017

argoneus commented Dec 19, 2017 •

edited

Loading

slack commented Dec 19, 2017

xszaboj commented Feb 15, 2018

alexanderknapstein commented Mar 9, 2018

evanlouie commented Mar 14, 2018

sauryadas commented Mar 14, 2018

SarahU commented Mar 19, 2018

jay-wilson commented Mar 21, 2018 •

edited

Loading

dmitrytokarev commented Apr 18, 2018 •

edited

Loading

adamkruszewski commented Apr 19, 2018 •

edited

Loading

kwal commented Apr 19, 2018

dad045 commented Apr 19, 2018 •

edited

Loading

Not possible to create aks cluster #38

Not possible to create aks cluster #38

Comments

aumanjoa commented Nov 11, 2017

seanmck commented Nov 12, 2017

sauryadas commented Nov 13, 2017

tmcgannon commented Nov 13, 2017

sauryadas commented Nov 14, 2017

tmcgannon commented Nov 14, 2017

aleksen commented Nov 14, 2017

Guillaume-Mayer commented Nov 14, 2017

sauryadas commented Nov 14, 2017

Guillaume-Mayer commented Nov 14, 2017 • edited Loading

slack commented Nov 14, 2017

Guillaume-Mayer commented Nov 17, 2017

bialad commented Nov 17, 2017

pjbgf commented Nov 18, 2017

frederimandin commented Nov 21, 2017

devonbarrett commented Nov 21, 2017

bytesofdhiren commented Nov 22, 2017

azzlack commented Nov 22, 2017

argoneus commented Dec 19, 2017 • edited Loading

slack commented Dec 19, 2017

xszaboj commented Feb 15, 2018

alexanderknapstein commented Mar 9, 2018

evanlouie commented Mar 14, 2018

sauryadas commented Mar 14, 2018

SarahU commented Mar 19, 2018

jay-wilson commented Mar 21, 2018 • edited Loading

dmitrytokarev commented Apr 18, 2018 • edited Loading

adamkruszewski commented Apr 19, 2018 • edited Loading

kwal commented Apr 19, 2018

dad045 commented Apr 19, 2018 • edited Loading

Guillaume-Mayer commented Nov 14, 2017 •

edited

Loading

argoneus commented Dec 19, 2017 •

edited

Loading

jay-wilson commented Mar 21, 2018 •

edited

Loading

dmitrytokarev commented Apr 18, 2018 •

edited

Loading

adamkruszewski commented Apr 19, 2018 •

edited

Loading

dad045 commented Apr 19, 2018 •

edited

Loading