Unable to create webapp. Linux workers are not available in resource group

mvhbharath commented 4 years ago

Hi Team,

When trying to create a linux app service in a new or existing resource group it constantly says: "Linux workers are not available in resource group xxxxxx. Use this link to learn more https://go.microsoft.com/fwlink/?linkid=831180" yet this page provides no real information on the error.

Use this link to learn more https://go.microsoft.com/fwlink/?linkid=831180 Please let me know why I am not able to create a web app under my existing resource group. I was able to do this before i.e I had both our web app and cosmos db running under the same resource group.

When I did a look up on this, it appears to have happened before. see here: https://github.com/MicrosoftDocs/azure-docs/issues/36268

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ef9002ed-c817-c615-fe32-05ad4cc78b61
Version Independent ID: 72295255-8d90-a2c6-0995-0e1208fcdcab
Content: Introduction to App Service on Linux - Azure
Content Source: articles/app-service/containers/app-service-linux-intro.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

SteeredKing commented 4 years ago

I face the exact same issue

DillonN commented 4 years ago

I'm having the same issue right now. So it seems you can't mix Linux and Windows workers within a resource group, app service plan, or region. But I deleted every resource that had anything to do with app services and still get the issue

I have tried:

Making a new resource group
Using many different regions
Selecting many different sizes
Combinations of all the above

And still get that message. So it seems like there is just an issue with making Linux workers right now, and it is giving that message because it doesn't know what the problem is. At least that's what #36268 would suggest, apparently they fixed the underlying issue back then but did not fix the fact that this misleading message will show for any unknown error

EDIT: I was able to deploy using the create new publish profile tool in Visual Studio. So it seems the problem is just limited to the portal.

jmasengesho commented 4 years ago

I am having this same issue. I am very sure that last night i was able to create a Web App resource for a linux image from container registry and it worked. A few hours later, it cannot work.

salochara commented 4 years ago

Having the same exact issue right now. @DillonN could you be more specific on how you solved this issue ? Thanks!

SnehaAgrawal-MSFT commented 4 years ago

@mvhbharath Thanks for the feedback! We are currently investigating and will update you shortly.

jmasengesho commented 4 years ago

@SnehaAgrawal-MSFT has this been resolved? Thanks

mvhbharath commented 4 years ago

Looks like the issue is resolved, I am able to create a linux app service in a new or existing resource group. @SnehaAgrawal-MSFT please let us know the root cause, since we were hard down and do not want it to happen again after we go live.

jmasengesho commented 4 years ago

It seems to work for me as well.

neilmiddleton-klaw commented 4 years ago

Not working for me this past two days. Tried creating Basic B1 in West Europe or UK South, neither working. Trying different SKUs I did get an S1 Standard into UK South, A Standard S1 did not work in West Europe.

I need my ASP in West Europe where these SKUs do not seem to work at the moment.

Code="BadRequest" Message="Requested feature is not available in resource group RG-XYZ.... Please try using a different resource group or create a new one." Details=[{"Message":"Requested feature is not available in resource group RG-XYZ..... Please try using a different resource group or create a new one."},{"Code":"BadRequest"},{"ErrorEntity":{"Code":"BadRequest","ExtendedCode":"59324","Message":"Requested feature is not available in resource group RG-XYZ.... Please try using a different resource group or create a new one.","MessageTemplate":"Requested feature is not available in resource group {0}. Please try using a different resource group or create a new one.","Parameters":[" RG-XYZ...."]}}]

SnehaAgrawal-MSFT commented 4 years ago

@mvhbharath & @jmasengesho Yes, there was an internal issue which is now been mitigated. @neilmiddleton-klaw request you to try it again it should work. Thanks again for bringing this to our attention. We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

oviliz commented 4 years ago

@SnehaAgrawal-MSFT , I'm having this exact problem in West Europe...

joshsten commented 4 years ago

@SnehaAgrawal-MSFT I believe I am also hitting this issue. Changing SKUs alone sometimes seems to work, and sometimes not.

joshsten commented 4 years ago

Note that bottom part. It's quite interesting.

Ratomir commented 4 years ago

I think that this issue should be reopened. I am having the exact same issue, but now with Azure Functions. I can't have two different functions operating on Windows and Linux in the same resource group and location. I am getting an error message as in the first message. You can following the same thread here. https://feedback.azure.com/forums/169385-web-apps/suggestions/37287583-allow-a-linux-and-windows-app-service-plan-to-exis

JiwanMS commented 4 years ago

I am facing similar issues in one of my resource groups. I have tried deleting all the exisitng app service, function app and app service plan but i still get the error "LinuxWorkersNotAllowedInResourceGroup" with tracking Id '4b10a5cc-af00-4c20-a26c-a3da95e60d04'. Please let me know if i need to open a new issue for this.

oviliz commented 4 years ago

@JiwanMS , are you creating the Linux App Service Plan in a different region from the one the main Windows App Service Plan is or was?

I've seen that sometimes M$ becomes confused when deleting resources and is impossible to replicate as is all inconsistent. They are but not...

gstevens-kyriba commented 4 years ago

OH, BUT IT IS POSSIBLE....

NAME TYPE LOCATION asp-kyr-gwy-qa App Service plan Linux ASP West US 2 kyr-cashflow-qa Service Fabric cluster Linux SF Cluster West US 2 kyr-cashflow-qa-nsg Network security group NSG West US 2 kyr-frontend-qa App Service plan Windows ASP West US 2 kyr-frontend-qa App Service Windows App Service West US 2 kyr-gateway-qa Public IP address IP West US 2 kyr-gwy-qa App Service Linux WebApp FC West US 2 kyr-qa-cashflow-vault Key vault KV West US 2 LB-kyr-cashflow-qa-Main Load balancer LB West US 2 LBIP-kyr-cashflow-qa-Main Public IP address IP West US 2 Main Virtual machine scale set VMSS West US 2 sfdgkyrcashflowqa8460 Storage account Storage West US 2 sflogskyrcashflowqa5569 Storage account Storage West US 2 VNet-kyr-cashflow-qa Virtual network VNET West US 2

JiwanMS commented 4 years ago

@oviliz Yes, I am creating the app service plan in the same region. There are a number of other resources in that RG and it wont be possible to delete everything. I have tried deleting all the app service, functions and app service plan. I am going to run the test again this weekend and provide you with the tracking ID that i get from the error while creating the linux app service plan.

oviliz commented 4 years ago

@JiwanMS , try creating it in a different region, in the same Resource Group. That's the only it worked for us despite what @gstevens-kyriba is saying. Maybe it works fine in the West US...

ArneKlein commented 4 years ago

For everybody who was struggling like me with an ARM template, the solution was 2-fold:

Always use a new resource group name, once you had this error (recommended not required, but there were some issues in the past)
Make sure, to set the app service to reserved as mentioned here https://github.com/terraform-providers/terraform-provider-azurerm/issues/3379, e.g.

{
      "apiVersion": "2018-02-01",
      "name": "[parameters('hostingPlanName')]",
      "type": "Microsoft.Web/serverfarms",
      "location": "[resourceGroup().location]",
      "kind": "linux",
      "sku":
      {
        "Name": "[parameters('skuCode')]",
        "capacity": "[parameters('skuCapacity')]"
      },
      "properties":
      {
        "name": "[parameters('hostingPlanName')]",
        "reserved": true
      }
    }

iBrooks commented 4 years ago

This needs to be reopened, The issue persists. Cannot deploy a linux app service in a resource group with a windows service in the same region.

neilmiddleton-klaw commented 4 years ago

seems MS put you into a "hardware cluster specific to an OS"- (MS please state if this is not correct as its anecdotal evidence on my part) I had to delete the whole RG, wait for a while (because Azure seemed to "remember") then deploy it all again. Or deploy it into another region completely (not ideal). But, essentially, the truth is that you cant have both linux and windows App Services in the same Resource group.

finesse-fingers commented 4 years ago

This looks like a known limitation. See docs https://docs.microsoft.com/en-us/azure/app-service/overview#limitations. Perhaps you can consider a different strategy when creating your resource groups.

troll-os commented 3 years ago

I have a Linux Plan in my RG with a Web App and I face the same issue in West Europe trying to add Linux Functions, where we already deployed models like this in the past...

lordpansar commented 3 years ago

This issue should be reopened. The problem still remains, I can't add a Linux function app in the same region (west europe) as my resource group. There's a reason why I would like my services to be in the same region, why should I have to spread them out across the globe? @SnehaAgrawal-MSFT

troll-os commented 3 years ago

This issue should be reopened. The problem still remains, I can't add a Linux function app in the same region (west europe) as my resource group. There's a reason why I would like my services to be in the same region, why should I have to spread them out across the globe? @SnehaAgrawal-MSFT

Did you try with the CLI ? I managed to create it with the CLI, I think there is something wrong at the portal level.

ctrlaltdan commented 3 years ago

I can reproduce this problem easily by:

Create new resource group
Add a certificate to your new resource group
Try and add a new app service plan (linux)

This took me a few hours to debug (through terraform) but can easily be reproduced by attaching/detaching the certificate from the resource group.

burakkarakus commented 3 years ago

In my case this error was thrown in the following scenario:

I have two Linux Azure Functions with App Service Plan. I tried to create another Linux Azure Function with Consumption Plan(Serverless), and I got the error above. I guess the error is the same as the OP's but the source of the problem is different. Anyone faced an issue liked this?

amkondi commented 3 years ago

hello Team,

i am facing the same issue, is there any solution to bypasse the probleme ?

error message : New-AzureRmResourceGroupDeployment : 18:06:06 - Error: Code=LinuxDynamicWorkersNotAllowedInResourceGroup; Message=Linux dynamic workers are not available in resource group XXXX Use this link to learn more http://go.microsoft.com/fwlink/?LinkId=825764.

BeigeBadger commented 3 years ago

In my case this error was thrown in the following scenario:

I have two Linux Azure Functions with App Service Plan. I tried to create another Linux Azure Function with Consumption Plan(Serverless), and I got the error above. I guess the error is the same as the OP's but the source of the problem is different. Anyone faced an issue liked this?

Yep, I ran into this issue - I ended up created a Windows Consumption plan so that I could continue working.. even though I already had a Linux App Service Plan with a Web App on Containers running in the same region and resource group. It's a little confusing. 😕

heinrich-ulbricht commented 2 years ago

Ran into this today as well.

fegu commented 2 years ago

The comment by @ctraltdan is correct, I confirmed this to be my problem as well. The solution is then to delete the certificate by going to resources.azure.com as described e.g. here and voila I can create the linux consumption plan.

phatcher commented 1 year ago

Hit this today trying to change a Linux service plan from P1v3 to P1mv3 - I think they are not only locking the resource group to an OS but to some internal allocation unit which then has certain capabilities, something similar happened when the Premium V3 service plans were introduced and you couldn't upgrade from Premium V2

iisalazar commented 10 months ago

I ran into this issue as well (for function app). I don't have a solution yet, but I plan to just deploy the Function app on a windows host

jutichok commented 8 months ago

I ran into the same problem. Any ideas on how to fix it? I've tried different things, like creating an M1V3 in a new resource group and moving the web app there, but it's still not doing the trick. I found some discussions suggesting I might have to recreate all the web apps, but I really don't want to go through that hassle if there's another way.

phatcher commented 8 months ago

@jutichok I think you will have to re-create the web app; if you move it brings along the scale set information that it was created with and then won't accept the new SKU, see https://learn.microsoft.com/en-gb/azure/app-service/app-service-configure-premium-tier#scale-up-from-an-unsupported-resource-group-and-region-combination

MicrosoftDocs / azure-docs

Unable to create webapp. Linux workers are not available in resource group #43248

Document Details