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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ Upgrading the AKSArc cluster. This operation might take a while...
47
47
48
48
## Possible causes and follow-ups
49
49
50
-
- The root cause is a recent change introduced in Azure Local version 2503. Under certain conditions, transient or intermittent failures during the Kubernetes upgrade process are not correctly detected or recovered from, leading the cluster state to remain indefinitely in the 'Upgrading' state.
50
+
- The root cause's 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.
51
51
- You hit this issue if the version of the AKS Arc extension on your custom location - the `hybridaksextension` extension's version is 2.1.211 or 2.1.223. You can run the following command to check the extension version on your cluster:
52
52
53
53
```azurecli
@@ -59,14 +59,14 @@ az k8s-extension show -g $res.HybridaksExtension.resourceGroup -c $res.ResourceB
59
59
60
60
61
61
## Mitigation
62
-
This issue can be resolved by invoking the AKS Arc update call. The `update` command will retrigger the upgrade flow as well. You can invoke the `aksarc update` command with some placeholder parameters. So in this case, you could invoke the update call to enable NFS or SMB drivers if those features are not already enabled. First, check whether any of the features enabled
62
+
This issue can be resolved by invoking the AKS Arc update call. The `update` command will retrigger the upgrade flow as well. You can invoke the `aksarc update` command with some placeholder parameters. 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 whether any of the features enabled
63
63
64
64
```azurecli
65
65
az login --use-device-code --tenant <Azure tenant ID>
66
66
az account set -s <subscription ID>
67
67
az aksarc show -g <resource_group_name> -n <cluster_name>
68
68
```
69
-
Check the storage profile setion:
69
+
Check the storage profile section:
70
70
```json
71
71
"storageProfile": {
72
72
"nfsCsiDriver": {
@@ -79,7 +79,7 @@ Check the storage profile setion:
79
79
}
80
80
```
81
81
82
-
If one of the drivers are disabled, you can enable it using the following command
82
+
If one of the drivers is disabled, you can enable it using the following command:
83
83
84
84
```azurecli
85
85
az aksarc update --enable-smb-driver -g <resource_group_name> -n <cluster_name>
0 commit comments