|
1 | 1 | --- |
2 | | -title: Troubleshoot the VirtualNetworkNotInSucceededState error code |
3 | | -description: Learn how to troubleshoot the VirtualNetworkNotInSucceededState error code when you create, upgrade or scale an Azure Kubernetes Service (AKS) cluster or node pool. |
| 2 | +title: Troubleshoot the VirtualNetworkNotInSucceededState Error Code |
| 3 | +description: Learn how to troubleshoot the VirtualNetworkNotInSucceededState error when you create, upgrade, or scale an Azure Kubernetes Service (AKS) cluster or node pool. |
4 | 4 | ms.date: 08/05/2025 |
5 | 5 | editor: v-jsitser |
6 | 6 | ms.reviewer: v-liuamson |
7 | 7 | ms.service: azure-kubernetes-service |
8 | | -#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the VirtualNetworkNotInSucceededState error code so that I can successfully create upgrade or scale an Azure Kubernetes Service (AKS) cluster or node pool. |
| 8 | +#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the VirtualNetworkNotInSucceededState error so that I can successfully create, upgrade, or scale an Azure Kubernetes Service (AKS) cluster or node pool. |
9 | 9 | ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool) |
10 | 10 | --- |
11 | | -# Troubleshoot the VirtualNetworkNotInSucceededState error code |
| 11 | +# Troubleshoot the VirtualNetworkNotInSucceededState error |
12 | 12 |
|
13 | 13 | ## Symptoms |
14 | 14 |
|
15 | | -When you create, upgrade or scale an Azure Kubernetes Service (AKS) |
16 | | -cluster or node pool, the deployment fails with an error like the |
17 | | -following: |
| 15 | +When you create, upgrade, or scale an Azure Kubernetes Service (AKS) cluster or node pool, the deployment fails and returns an error message that resembles the |
| 16 | +following message: |
18 | 17 |
|
19 | 18 | *Status=400 Code=\"VirtualNetworkNotInSucceededState\"* |
20 | 19 |
|
21 | | -*Message=\"Set virtual network ownership failed. Subscription: |
22 | | -\<SUBSCRIPTION\>; resource group: \<RESOURCE GROUP\>; virtual network |
23 | | -name: \<VNET NAME\>. autorest/azure: Service returned an error. |
24 | | -Status=400 Code=\"VirtualNetworkNotInSucceededState\" Message=\"Virtual |
25 | | -network /subscriptions/\<SUBSCRIPTION\>/resourceGroups/\<RESOURCE |
26 | | -GROUP\>/providers/Microsoft.Network/virtualNetworks/\<VNET\> is in |
27 | | -Updating state. It needs to be in Succeeded state in order to set |
28 | | -resource ownership.* |
| 20 | +*Message=\"Set virtual network ownership failed. Subscription: \<SUBSCRIPTION\>; resource group: \<RESOURCE GROUP\>; virtual network name: \<VNET NAME\>. autorest/azure: Service returned an error. |
| 21 | +Status=400 Code=\"VirtualNetworkNotInSucceededState\" Message=\"Virtual network /subscriptions/\<SUBSCRIPTION\>/resourceGroups/\<RESOURCE |
| 22 | +GROUP\>/providers/Microsoft.Network/virtualNetworks/\<VNET\> is in Updating state. It needs to be in Succeeded state in order to set resource ownership.* |
29 | 23 |
|
30 | 24 | ## Cause |
31 | 25 |
|
32 | | -AKS can set ownership on a virtual network only when the |
33 | | -`provisioningState` of the VNet is **Succeeded**. The request fails if the |
34 | | -VNet is in **Updating, Deleting or Failed**. Common reasons include: |
| 26 | +AKS can set ownership on a virtual network only if the `provisioningState` of the VNet is **Succeeded**. The request fails if the VNet is in the **Updating**, **Deleting**, or **Failed** state. Common causes for this condition include: |
35 | 27 |
|
36 | | -- Another create, update, or delete operation is still running on the |
37 | | - VNet. |
| 28 | +- Another create, update, or delete operation is still running on the VNet. |
38 | 29 |
|
39 | | -- A previous network operation failed and left the VNet in the **Failed** |
40 | | - state. |
| 30 | +- A previous network operation failed and left the VNet in the **Failed** state. |
41 | 31 |
|
42 | | -- Multiple parallel cluster or node‑pool deployments are trying to |
43 | | - modify the same VNet at the same time. |
| 32 | +- Multiple parallel cluster or node‑pool deployments are trying to modify the same VNet at the same time. |
44 | 33 |
|
45 | 34 | ## Resolution |
46 | 35 |
|
47 | 36 | Check the current provisioning state of the VNET: |
48 | 37 |
|
49 | | -*az network vnet show -g \<resource-group\> -n \<vnet-name\> \--query |
50 | | -\"provisioningState\" -o tsv* |
| 38 | +*az network vnet show -g \<resource-group\> -n \<vnet-name\> \--query \"provisioningState\" -o tsv* |
51 | 39 |
|
52 | | -If the command returns **Succeeded**, retry your AKS operation. If it |
53 | | -returns any other value. For more guidance, you may follow the troubleshooting steps described in [Troubleshoot Azure Microsoft.Network failed provisioning state](/azure/networking/troubleshoot-failed-state). |
| 40 | +If the command returns **Succeeded**, retry your AKS operation. If it returns any other value. For more guidance, follow the troubleshooting steps in [Troubleshoot Azure Microsoft.Network failed provisioning state](/azure/networking/troubleshoot-failed-state). |
54 | 41 |
|
55 | | -[!INCLUDE [azure-help-support](../../../includes/azure-help-support.md)] |
| 42 | +[!INCLUDE [azure-help-support](../../../includes/azure-help-support.md)] |
0 commit comments