Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
Symptoms
During cluster creation or node pool creation and scale operations, you might see the following error message:
The system failed to create <Azure resource name>: There is not enough space on the disk.
Cause
The issue is caused by a recent regression introduced in Azure Local, version 2506.
Mitigation
This issue was fixed in AKS on Azure Local, version 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.
Workaround for Azure Local version 2506
This issue only affects clusters in Azure Local version 2506. Install the support module and run the commands provided in this module.
First, run the following command to check for known issues in your AKS Arc environment:
Test-SupportAksArcKnownIssues
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:
Invoke-SupportAksArcRemediation
Verification
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
If the problem persists, collect the AKS cluster logs before you create a support request.