Failed to deploy Tier 1 devbox cloud-hosted environment in LCS
Evaldas
1,800
Like
Share
ReportHello AX World,
This will be a short but hopefully helpful post to the ones who face this issue.
Recently I failed to deploy a cloud-hosted environment in LCS.
I wanted to deploy a standard devbox (Tier 1) with the latest Platform Update (PU35). It was recently made GA.
I started to create one.
I gave it a name, changed the size from the default D13 to the DS12 v2, which I heard some time ago was a cheaper alternative without performance reduction, or even performing better for D365F. But this post is not about that. I cannot prove that; I did not test it myself.
Fast-forward within an hour or so, it failed. It was the first time I saw this.
I thought, maybe it's a one-time temporary glitch, so I tried couple more times.
It failed again!
The only error message I could see was this:
Error code: 0
Error message: Failed to fetch deployment error from outputXml.
It showed zero virtual machines deployed and it was missing some information, like local accounts etc.
Next, instead of DS12 v2, I tried the default D13, but it did not even let me start the deployment. It gave me the following error:
The current subscription id [subscription id] does not allow the VM SKUs [Standard_D13], either because they don't exist in the current region or because of the of the restriction codes [NotAvailableForSubscription;NotAvailableForSubscription]. Please open a ticket with Azure Support to enable these SKUs in your subscription. If the issue persists, please contact support with this id:[activity id]
I asked for some help on Joris (@jorisdg) post on Twitter and luckily enough I got some helpful hints by Teemu (@TeemuPMiettinen) and Lane (@LaneSwenka). Thanks to them and don't forget to follow them on Twitter.
They gave me hints that it might be related to Azure subscription, geo restrictions, policies or quotas etc.
The last error was quite clear. The D13 size was not available in the region (West Europe) or not available in the subscription. I rested the case for D13 and focused on the other configuration.
I asked our Azure Subscription admins to check what could be wrong.
Fast forward I was told that recently there was a new policy enforced, that did not allow Resource Groups to be created if they did not have tags on them.
As you know when you deploy a cloud hosted environment a resource group is created with the same name as the environment name and there is no other way to create it (to my knowledge).
If you pre-create them, you will get the following error:
Lifecycle Services tried to deploy the environment, but there is already an existing group with name [resource group name]. ...
The solution was to temporary disable the policy, deploy the environment and enable it again.
However, this is not a nice solution. I wish I could come up with something more creative.
Be aware and take care!
This will be a short but hopefully helpful post to the ones who face this issue.
The problem
Recently I failed to deploy a cloud-hosted environment in LCS.
I wanted to deploy a standard devbox (Tier 1) with the latest Platform Update (PU35). It was recently made GA.
I started to create one.
I gave it a name, changed the size from the default D13 to the DS12 v2, which I heard some time ago was a cheaper alternative without performance reduction, or even performing better for D365F. But this post is not about that. I cannot prove that; I did not test it myself.
Fast-forward within an hour or so, it failed. It was the first time I saw this.
I thought, maybe it's a one-time temporary glitch, so I tried couple more times.
It failed again!
The only error message I could see was this:
Error code: 0
Error message: Failed to fetch deployment error from outputXml.
It showed zero virtual machines deployed and it was missing some information, like local accounts etc.
Next, instead of DS12 v2, I tried the default D13, but it did not even let me start the deployment. It gave me the following error:
The current subscription id [subscription id] does not allow the VM SKUs [Standard_D13], either because they don't exist in the current region or because of the of the restriction codes [NotAvailableForSubscription;NotAvailableForSubscription]. Please open a ticket with Azure Support to enable these SKUs in your subscription. If the issue persists, please contact support with this id:[activity id]
They gave me hints that it might be related to Azure subscription, geo restrictions, policies or quotas etc.
The root cause
The last error was quite clear. The D13 size was not available in the region (West Europe) or not available in the subscription. I rested the case for D13 and focused on the other configuration.
I asked our Azure Subscription admins to check what could be wrong.
Fast forward I was told that recently there was a new policy enforced, that did not allow Resource Groups to be created if they did not have tags on them.
As you know when you deploy a cloud hosted environment a resource group is created with the same name as the environment name and there is no other way to create it (to my knowledge).
If you pre-create them, you will get the following error:
Lifecycle Services tried to deploy the environment, but there is already an existing group with name [resource group name]. ...
"Solution"
The solution was to temporary disable the policy, deploy the environment and enable it again.
However, this is not a nice solution. I wish I could come up with something more creative.
Be aware and take care!
This was originally posted here.
*This post is locked for comments