I am cross posting from:
Azure/AKS#5612
What happened:
Not sure if the error is specific to WS2025, but I've never seen this before on WS2022. Unable to schedule any new pods after the error starts showing up.
Warning FailedMount 6m50s (x13 over 17m) kubelet MountVolume.SetUp failed for volume "log" : rpc error: code = Internal desc = volume(csi-21bed4d53ca16a95d6b7c405d04eb430f7467926f3479efdfe191d5fffa41e5f) mount \\xxx.file.core.windows.net\applog on c:\var │
│ \lib\kubelet\pods\dab626fb-e228-4176-8fe1-6ec262b945fd\volumes\kubernetes.io~csi\log\mount failed with NewSmbGlobalMapping failed. output: "New-SmbGlobalMapping : Multiple connections to a server or shared resource by the same user, using more than one user \r\nname, are not │
│ allowed. Disconnect all previous connections to the server or shared resource and try again. \r\nAt line:1 char:190\r\n+ ... ser, $PWord;New-SmbGlobalMapping -RemotePath $Env:smbremotepath -Cred ...\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ │
│ ~\r\n + CategoryInfo : NotSpecified: (MSFT_SmbGlobalMapping:ROOT/Microsoft/...mbGlobalMapping) [New-SmbGlobalMa \r\n pping], CimException\r\n + FullyQualifiedErrorId : Windows System Error 1219,New-SmbGlobalMapping\r\n \r\n", err: exit status 1 │
│ Please refer to http://aka.ms/filemounterror for possible causes and solutions for mount errors.
What you expected to happen:
No errors.
How to reproduce it:
N/A
Anything else we need to know?:
Environment:
- CSI Driver version: mcr.microsoft.com/oss/v2/kubernetes-csi/azurefile-csi:v1.33.7-windows-hp
- Kubernetes version (use
kubectl version): 1.33.3
I am cross posting from:
Azure/AKS#5612
What happened:
Not sure if the error is specific to WS2025, but I've never seen this before on WS2022. Unable to schedule any new pods after the error starts showing up.
What you expected to happen:
No errors.
How to reproduce it:
N/A
Anything else we need to know?:
Environment:
kubectl version): 1.33.3