You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this article, you'll troubleshoot allocation failures where a Virtual Machine (VM) size isn't available when you deploy an Azure Cloud service (classic).
19
+
This article troubleshoots allocation failures where a virtual machine (VM) size isn't available when you deploy an Azure Cloud service (classic).
18
20
19
21
When you deploy instances to a Cloud service (classic) or add new web or worker role instances, Microsoft Azure allocates compute resources.
20
22
21
-
You may occasionally receive errors during these operations even before you reach the Azure subscription limit.
23
+
You might receive errors during these operations even before you reach the Azure subscription limit.
22
24
23
25
> [!TIP]
24
26
> The information may also be useful when you plan the deployment of your services.
25
27
26
28
## Symptom
27
29
28
-
In Azure portal, navigate to your Cloud service (classic) and in the sidebar select *Operation log (classic)* to view the logs.
30
+
In the [Azure portal](https://portal.azure.com/), navigate to your Cloud service (classic) and in the sidebar select **Operation log (classic)** to view the logs.
29
31
30
-
32
+
:::image type="content" source="./media/cloud-services-troubleshoot-location-not-found-for-role-size/cloud-services-troubleshoot-allocation-logs.png" alt-text="Screenshot shows the Operation log (classic) pane.":::
31
33
32
-
When you're inspecting the logs of your Cloud service (classic), you'll see the following exception:
34
+
When you inspect the logs of your Cloud service (classic), you'll see the following exception:
33
35
34
36
|Exception Type |Error Message |
35
37
|---------|---------|
36
-
|LocationNotFoundForRoleSize |The operation '`{Operation ID}`' failed: 'The requested VM tier is currently not available in Region (`{Region ID}`) for this subscription. Please try another tier or deploy to a different location.'.|
38
+
|`LocationNotFoundForRoleSize`|The operation '`{Operation ID}`' failed: 'The requested VM tier is currently not available in Region (`{Region ID}`) for this subscription. Please try another tier or deploy to a different location.'.|
37
39
38
40
## Cause
39
41
40
-
There's a capacity issue with the region or cluster that you're deploying to. The *LocationNotFoundForRoleSize* exception occurs when the resource SKU you've selected (VM size) isn't available for the region specified.
42
+
There's a capacity issue with the region or cluster that you're deploying to. The `LocationNotFoundForRoleSize` exception occurs when the resource SKU you've selected, the virtual machine size, isn't available for the region specified.
41
43
42
-
## Solution
44
+
## Find SKUs in a region
43
45
44
-
In this scenario, you should select a different region or SKU to deploy your Cloud service (classic) to. Before deploying or upgrading your Cloud service (classic), you can determine which SKUs are available in a region or availability zone. Follow the [Azure CLI](#list-skus-in-region-using-azure-cli), [PowerShell](#list-skus-in-region-using-powershell), or [REST API](#list-skus-in-region-using-rest-api) processes below.
46
+
In this scenario, you should select a different region or SKU for your Cloud service (classic) deployment. Before you deploy or upgrade your Cloud service (classic), determine which SKUs are available in a region or availability zone. Follow the [Azure CLI](#list-skus-in-region-using-azure-cli), [PowerShell](#list-skus-in-region-using-powershell), or [REST API](#list-skus-in-region-using-rest-api) processes below.
45
47
46
48
### List SKUs in region using Azure CLI
47
49
48
-
You can use the [az vm list-skus](/cli/azure/vm
49
-
#az-vm-list-skus) command.
50
+
You can use the [az vm list-skus](/cli/azure/vm#az-vm-list-skus) command.
50
51
51
52
- Use the `--location` parameter to filter output to location you're using.
52
53
- Use the `--size` parameter to search by a partial size name.
53
54
- For more information, see the [Resolve error for SKU not available](../azure-resource-manager/templates/error-sku-not-available.md#solution-2---azure-cli) guide.
54
55
55
-
**For example:**
56
+
This sample command produces the following results:
56
57
57
-
```azurecli
58
-
az vm list-skus --location southcentralus --size Standard_F --output table
59
-
```
58
+
```azurecli
59
+
az vm list-skus --location southcentralus --size Standard_F --output table
60
+
```
60
61
61
-
**Example results:**
62
-
62
+
:::image type="content" source="./media/cloud-services-troubleshoot-constrained-allocation-failed/cloud-services-troubleshoot-constrained-allocation-failed-1.png" alt-text="Screenshot shows the Azure CLI output of running the command, which shows the available SKUs.":::
63
63
64
64
#### List SKUs in region using PowerShell
65
65
@@ -69,21 +69,19 @@ You can use the [Get-AzComputeResourceSku](/powershell/module/az.compute/get-azc
69
69
- You must have the latest version of PowerShell for this command.
70
70
- For more information, see the [Resolve error for SKU not available](../azure-resource-manager/templates/error-sku-not-available.md#solution-1---powershell) guide.
71
71
72
-
**For example:**
72
+
This command filters by location:
73
73
74
74
```azurepowershell
75
75
Get-AzComputeResourceSku | where {$_.Locations -icontains "centralus"}
76
76
```
77
77
78
-
**Some other useful commands:**
79
-
80
-
Filter out the locations that contain size (Standard_DS14_v2):
78
+
Find the locations that contain the size `Standard_DS14_v2`:
81
79
82
80
```azurepowershell
83
81
Get-AzComputeResourceSku | where {$_.Locations.Contains("centralus") -and $_.ResourceType.Contains("virtualMachines") -and $_.Name.Contains("Standard_DS14_v2")}
84
82
```
85
83
86
-
Filter out all the locations that contain size (V3):
84
+
Find the locations that contain the size `V3`:
87
85
88
86
```azurepowershell
89
87
Get-AzComputeResourceSku | where {$_.Locations.Contains("centralus") -and $_.ResourceType.Contains("virtualMachines") -and $_.Name.Contains("v3")} | fc
@@ -129,4 +127,4 @@ For more allocation failure solutions and to better understand how they're gener
129
127
> [!div class="nextstepaction"]
130
128
> [Allocation failures - Cloud service (classic)](cloud-services-allocation-failures.md)
131
129
132
-
If your Azure issue isn't addressed in this article, visit the Azure forums on [MSDN and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
130
+
If your Azure issue isn't addressed in this article, visit the Azure forums on [MSDN and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select **Get support**.
0 commit comments