[BUG] Access to the path '.Moc' is denied.
- Dominant language
- PowerShell
- Stars
- 118
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Very strange,
"Applying platform configurations failed. Error: Access to the path '.Moc' is denied."
**To Reproduce**
Steps to reproduce the behavior:
just trying to deploy AKS service on Azure Stakc HCI
**Expected behavior**
Deploy Kubernetes Service should work from command line or from WAC
**Screenshots**
From Wac
Edge


Chrome

from PSWH

created new volume02
that didn't work
but when I created "volume1" it worked

to be clear I used volume01 in my command (and in WAC, I don't even get a choice, its a drop down)
but when I create a new volume called "volume1" files appeared while using the volume01 in the command

**Environment (please complete the following information):**
- OS: Azure Stack HCI 20349.1850
- Browser Edge & chrome,
- AKS-HCI Version 1.1.81
- Kubernetes Version 1.25.7
**Additional context**


**Collect log files**
- From a PowerShell Admin window run **Get-AksHciLogs**
[](URL)
I actually fully redeployed these host from scratch and got the same results.
Contributor guide
Research direction
Start by reproducing the AKS deployment on Azure Stack HCI 20349.1850 with AKS-HCI 1.1.81 and Kubernetes 1.25.7, comparing volume01 with volume1 from PowerShell and WAC. Collect logs with Get-AksHciLogs and use them to investigate the '.Moc' access-denied error. Done means identifying the cause and documenting a verified fix or reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, powershell
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100