Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update file-share-mount-failures-azure-files.md #1674

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update file-share-mount-failures-azure-files.md #1674

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c42f67
Update file-share-mount-failures-azure-files.md
Oct 23, 2024
ba345e6
Update file-share-mount-failures-azure-files.md
Oct 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions support/azure/azure-kubernetes/storage/file-share-mount-failures-azure-files.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
title: File share mounting failures for Azure Files
description: Troubleshoot why your file share for Azure Files fails to mount as storage on your Azure Kubernetes Service (AKS) clusters.
ms.date: 06/10/2022
ms.reviewer: chiragpa, nickoman, v-leedennis
ms.date: 10/23/2024
ms.reviewer: chiragpa, nickoman, jaewonpark, v-leedennis
ms.service: azure-kubernetes-service
keywords:
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot why my file share fails to mount so that I can successfully use Azure Files for storage on my Azure Kubernetes Service (AKS) clusters.
Expand All @@ -16,6 +16,14 @@ This article discusses how to troubleshoot file share mounting failures for Azur

Your storage account key has changed.

## Symptom

This can occur as various errors, but the following event mainly occur in pods.

```
Error: failed to generate container "56907e9807c6f4203c3aace8c5a6e3a75832cf07d3080a3869d355114657b54f" spec: failed to generate spec: failed to stat "/var/lib/kubelet/pods/xxxxxxxx-9fe6-46d7-b12e-339951b8d2f5/volumes/kubernetes.io~csi/pvc-xxxxxxxx-3b70-498c-b357-3488e1c1f429/mount": stat /var/lib/kubelet/pods/xxxxxxxx-9fe6-46d7-b12e-339951b8d2f5/volumes/kubernetes.io~csi/pvc-xxxxxxxx-3b70-498c-b357-3488e1c1f429/mount: host is down
```

## Solution

Manually update the `azurestorageaccountkey` field in an Azure file secret with your base64-encoded storage account key. To make this update, follow these steps:
Expand All @@ -34,6 +42,11 @@ Manually update the `azurestorageaccountkey` field in an Azure file secret with

1. Change the `azurestorageaccountkey` field to use the new base64-encoded storage account key, and save the file.

1. Redeploy your pods.

> [!NOTE]
> Simply deleting the pod and let it recreate again may not take effect. Be sure to redeploy the pod.

After a few minutes, the agent node will retry the Azure File mount with the updated storage key.

[!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]
Expand Down