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
Copy file name to clipboardExpand all lines: AKS-Arc/tsg-aksarc-upgrade-issues.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,11 +11,11 @@ ms.reviewer: abha
11
11
12
12
# Troubleshoot the issue when the AKS Arc cluster is stuck in 'Upgrading' state
13
13
14
-
This article describes how to fix the issue when your Azure Kubernetes Service enablied by Arc (AKS Arc) cluster is stuck in 'Upgrading' state. This issue typically occurs after updating Azure Local to version 2503 or 2504 and when you try to upgrade the Kubernetes version on your cluster.
14
+
This article describes how to fix the issue when your Azure Kubernetes Service enabled by Arc (AKS Arc) cluster is stuck in 'Upgrading' state. This issue typically occurs after updating Azure Local to version 2503 or 2504 and when you try to upgrade the Kubernetes version on your cluster.
15
15
16
16
## Symptoms
17
17
18
-
When you try to upgrade an AKS Arc cluster, you notice that the **Current state** property of the cluster remains in the 'Upgrading' state.
18
+
When you try to upgrade an AKS Arc cluster, you notice that the **Current state** property of the cluster remains in the 'Upgrading' state.
19
19
20
20
```output
21
21
az aksarc upgrade --name "cluster-name" --resource-group "rg-name"
@@ -34,17 +34,16 @@ Upgrading the AKSArc cluster. This operation might take a while...
- The root cause is a recent change introduced in Azure Local version 2503. Under certain conditions, if there are transient or intermittent failures during the Kubernetes upgrade process, they're not correctly detected or recovered from. This can cause the cluster state to stay stuck in the 'Upgrading' state.
@@ -57,16 +56,18 @@ $res=get-archcimgmt
57
56
az k8s-extension show -g $res.HybridaksExtension.resourceGroup -c $res.ResourceBridge.name --cluster-type appliances --name hybridaksextension
58
57
```
59
58
60
-
61
59
## Mitigation
62
-
This issue can be resolved by invoking the AKS Arc update command. The `update` command will retriggers the upgrade flow. You can invoke the `aksarc update` command with placeholder parameters, which dont impact the state of the cluster. So in this case, you could invoke the update call to enable NFS or SMB drivers if those features aren't already enabled. First, check if any of the storage drivers are already enabled:
60
+
61
+
This issue can be resolved by invoking the AKS Arc update command. The `update` command retriggers the upgrade flow. You can invoke the `aksarc update` command with placeholder parameters, which do not impact the state of the cluster. So in this case, you could invoke the update call to enable NFS or SMB drivers if those features aren't already enabled. First, check if any of the storage drivers are already enabled:
63
62
64
63
```azurecli
65
64
az login --use-device-code --tenant <Azure tenant ID>
66
65
az account set -s <subscription ID>
67
66
az aksarc show -g <resource_group_name> -n <cluster_name>
68
67
```
68
+
69
69
Check the storage profile section:
70
+
70
71
```json
71
72
"storageProfile": {
72
73
"nfsCsiDriver": {
@@ -92,17 +93,18 @@ Running the `aksarc update` command should resolve the issue and the `Current st
92
93
az aksarc update --disable-smb-driver -g <resource_group_name> -n <cluster_name>
93
94
az aksarc update --disable-nfs-driver -g <resource_group_name> -n <cluster_name>
94
95
```
96
+
95
97
If both drivers are already enabled on your cluster, you can disable the one that is not in use. If you require both drivers to remain enabled, contact Microsoft Support for further assistance.
96
98
97
99
## Verification
100
+
98
101
Run the following command and check that the **Current State** parameter in the JSON output is set to 'Succeeded' to confirm the K8s version upgrade is complete.
99
102
100
103
```azurecli
101
104
az aksarc show -g <resource_group> -n <cluster_name>
102
105
103
106
```
104
107
105
-
106
108
## Contact Microsoft Support
107
109
108
110
If the problem persists, collect the following information before [creating a support request](aks-troubleshoot.md#open-a-support-request). Collect [AKS cluster logs](get-on-demand-logs.md) before creating the support request.
0 commit comments