Skip to content

Commit 41389f0

Browse files
Merge pull request #267657 from AbhishekMallick-MS/Feb-29-2024-AKS
AKS backup - Role name change
2 parents 81e256b + ed4d22c commit 41389f0

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Troubleshoot Azure Kubernetes Service backup
33
description: Symptoms, causes, and resolutions of the Azure Kubernetes Service backup and restore operations.
44
ms.topic: troubleshooting
5-
ms.date: 02/28/2024
5+
ms.date: 02/29/2024
66
ms.service: backup
77
ms.custom:
88
- ignite-2023
@@ -63,10 +63,10 @@ The extension pods aren't exempt, and require the Microsoft Entra pod identity t
6363
kubectl get Azurepodidentityexceptions --all-namespaces
6464
```
6565

66-
3. To assign the *Storage Account Contributor* role to the extension identity, run the following command:
66+
3. To assign the *Storage Blob Data Contributor* role to the extension identity, run the following command:
6767

6868
```azurecli-interactive
69-
az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name aksclustername --resource-group aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Account Contributor' --scope /subscriptions/subscriptionid/resourceGroups/storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/storageaccountname
69+
az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name aksclustername --resource-group aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Blob Data Contributor' --scope /subscriptions/subscriptionid/resourceGroups/storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/storageaccountname
7070
```
7171

7272
### Scenario 3
@@ -192,13 +192,13 @@ These error codes appear due to issues based on the Backup extension installed i
192192

193193
### UserErrorExtensionMSIMissingPermissionsOnBackupStorageLocation
194194

195-
**Cause**: The Backup extension should have the *Storage Account Contributor* role on the Backup Storage Location (storage account). The Extension Identity gets this role assigned.
195+
**Cause**: The Backup extension should have the *Storage Blob Data Contributor* role on the Backup Storage Location (storage account). The Extension Identity gets this role assigned.
196196

197197
**Recommended action**: If this role is missing, then use Azure portal or CLI to reassign this missing permission on the storage account.
198198

199199
### UserErrorBackupStorageLocationNotReady
200200

201-
**Cause**: During extension installation, a Backup Storage Location is to be provided as input that includes a storage account and blob container. The Backup extension should have *Storage Account Contributor* role on the Backup Storage Location (storage account). The Extension Identity gets this role assigned.
201+
**Cause**: During extension installation, a Backup Storage Location is to be provided as input that includes a storage account and blob container. The Backup extension should have *Storage Blob Data Contributor* role on the Backup Storage Location (storage account). The Extension Identity gets this role assigned.
202202

203203
**Recommended action**: The error appears if the Extension Identity doesn't have right permissions to access the storage account. This error appears if AKS backup extension is installed the first time when configuring protection operation. This happens for the time taken for the granted permissions to propagate to the AKS backup extension. As a workaround, wait an hour and retry the protection configuration. Otherwise, use Azure portal or CLI to reassign this missing permission on the storage account.
204204

0 commit comments

Comments
 (0)