Failed to save container service '<name>'. Error: The VM size of Agent is not allowed in your subscription in location 'westeurope'.

[Zimmergren]

I've been running AKS for a few months and have always used West Europe as a location for my resources and cluster. I've been running A4-sized clusters for a couple of things, and starting today we're seeing the below message when trying to scale out from N to Y nodes.

Current cluster config

• Size: Standard_A4
• Location: West Europe

Expected results
This has worked for a long time, so I would naively expect it to continue working.

Actual results
Failed with the below message.

Failed to save container service 'cloudcluster2'. Error: The VM size of Agent is not allowed in your subscription in location 'westeurope'. Agent VM size 'Standard_A4' is available in locations: centraluseuap,eastus,eastus2euap,southcentralus,westcentralus,westus2.

Is this a glitch in the matrix right now, or are the locations available to different VM sizes changing? If so, where is this being communicated so I can keep up with those changes?

[Zimmergren]

Update:
Trying to create a new cluster using the same setup, trying with different node sizes in West Europe specifically, we still get the error:

az aks create -g rg-weu-aks-a4mv2 -n cloudcluster-a4mv2 --location westeurope --node-vm-size Standard_A4m_v2

Yields this result:

Operation failed with status: 'Bad Request'. Details: The VM size of Agent is not allowed in your subscription in location 'westeurope'. Agent VM size 'Standard_A4m_v2' is available in locations: centraluseuap,eastus,eastus2euap,southcentralus,westcentralus,westus2.

Expected results

• I expect to be able to continue to create a cluster in West Europe

Actual Results

• I can not create a cluster in West Europe
• Triggering a creation of a new cluster in eastus works, but this is not what we desire.

[lehtiton]

I have the same issue. Using another region is not an option. Someone from Microsoft, please comment on this! What is the reason for this? This is not a first time I'm running this issue. I cannot do anything with AKS now!!!

[Zimmergren]

I've been in touch with MS support who's looking into this now. Might be a data center issue rather than AKS but they are working on it. I will follow up here once I receive more info. Sent from my Samsung Galaxy smartphone.

[LoungeFlyZ]

related? #280

[chryswoods]

I have the same issue. Deleted an existing westeurope AKS cluster so that I could create a new one with a different VM size and now get 'Bad Request' for every VM size I try. A2_v2, A4_v2,, A4m_v2 D4_v3 etc. all give the same errors. Also raised a service ticket with MS support. Cannot do anything with AKS at the moment. Have to run servers in Europe, and since northeurope doesn't support managed clusters, am pretty stuck now.

[chryswoods]

Support confirmed that this is related to issue #280. Suggested I try a different VM size (Av1, Av2, H, GS or LS) or another region.

[slack]

This is related to #280 closing this issue.

[linocatucci]

hi,
any updates on this issue?

Br,
Lino

[Zimmergren]

@linocatucci please see #280 which is describing the issue and reason. No solution as of writing this though.

[linocatucci]

great thank you for your quick response!

…

-- Lino Catucci Op 3 april 2018 bij 14:01:57, Tobias Zimmergren (notifications@github.com) schreef: @linocatucci <https://github.com/linocatucci> please see #280 <#280> which is describing the issue and reason. No solution as of writing this though. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#279 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ-gngJp9vHsbBiIbxBlaSmqlhEmyhBQks5tk2S0gaJpZM4S_z95> .