|
| 1 | +--- |
| 2 | +title: Troubleshoot issue in which storage provisioning fails |
| 3 | +description: Learn how to troubleshoot and mitigate an issue that occurs when storage provisioning fails. |
| 4 | +ms.topic: troubleshooting |
| 5 | +author: rcheeran |
| 6 | +ms.author: rcheeran |
| 7 | +ms.date: 07/23/2025 |
| 8 | +ms.reviewer: rcheeran |
| 9 | +ms.lastreviewed: 07/23/2025 |
| 10 | + |
| 11 | +--- |
| 12 | + |
| 13 | +# Troubleshoot storage provisioning issue during cluster and node pool creation |
| 14 | + |
| 15 | +This article describes an issue in which new AKS Arc nodes are created on a single storage path/volume of the Azure Local cluster, breaking the expected round-robin distribution among volumes. Over time, this might cause insufficient disk space on that path, potentially resulting in deployment failures. |
| 16 | + |
| 17 | +## Symptoms |
| 18 | + |
| 19 | +During cluster creation or node pool creation and scale operations, you might see the following error message: |
| 20 | + |
| 21 | +```output |
| 22 | +The system failed to create <Azure resource name>: There is not enough space on the disk. |
| 23 | +``` |
| 24 | + |
| 25 | +## Cause |
| 26 | + |
| 27 | +The issue is caused by a recent regression introduced in Azure Local, version 2506. |
| 28 | + |
| 29 | +## Mitigation |
| 30 | + |
| 31 | +This issue was fixed in AKS on [Azure Local, version 2507](/azure/azure-local/whats-new?view=azloc-2507&preserve-view=true#features-and-improvements-in-2507). However, this mitigation works only when you create new Azure Local instances with version 2507. Upgrading from Azure Local versions 2506 to 2507 does not resolve the issue. |
| 32 | + |
| 33 | +### Workaround for Azure Local version 2506 |
| 34 | + |
| 35 | +This issue only affects clusters in Azure Local version 2506. Install the [support module](support-module.md) and run the commands provided in this module: |
| 36 | + |
| 37 | +First, run the following command to check for known issues in your AKS Arc environment: |
| 38 | + |
| 39 | +```powershell |
| 40 | +Test-SupportAksArcKnownIssues |
| 41 | +``` |
| 42 | + |
| 43 | +Then, run the following command to fix this known issue on your deployment. This command finds all available fixes for the current version, and installs those fixes: |
| 44 | + |
| 45 | +```powershell |
| 46 | +Invoke-SupportAksArcRemediation |
| 47 | +``` |
| 48 | + |
| 49 | +## Verification |
| 50 | + |
| 51 | +Once the fix is done, you should be able to create your clusters and node pools. If you still encounter issues, please [reach out to Microsoft Support](#contact-microsoft-support). |
| 52 | + |
| 53 | +## Contact Microsoft Support |
| 54 | + |
| 55 | +If the problem persists, collect the [AKS cluster logs](get-on-demand-logs.md) before you [create a support request](aks-troubleshoot.md#open-a-support-request). |
| 56 | + |
| 57 | +## Next steps |
| 58 | + |
| 59 | +- [Use the diagnostic checker tool to identify common environment issues](aks-arc-diagnostic-checker.md) |
| 60 | +- [Review AKS on Azure Local architecture](cluster-architecture.md) |
0 commit comments