-
Notifications
You must be signed in to change notification settings - Fork 192
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.
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
Mounting Disks under NVMe diskcontroller in windows failes #2365
Comments
could it always repro on Standard_D4alds_v6 windows vm sku? |
hey @andyzhangx i've tried it 4-5 times with different machines in a vmss. I think there have been some changes on how managed disks are attached to the those VMs. Maybe this helps: Managed disk on
on the
I've removed the non-related entries to keep it simple and replaced them with |
@Flask so on |
Exactly. Storage class is in both cases:
|
@Flask I think there is sth. wrong with the windows vm internal config for this vm sku. Can you file a support ticket to Azure windows VM team? thx |
On linux, there should be a udev rule to detect data disk automatically: |
FYI. the nvme disk is already supported on Linux node with v1.30.3 release, still need to figure how to get the <lun, disk-num> mapping on Windows node. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What happened:
Trying to mount a managed disk on a nvme diskcontroller vm failes
Warning FailedMount 4m49s (x49 over 89m) kubelet MountVolume.MountDevice failed for volume "pvc-dcdeeaa3-cd7a-40ff-8e4e-3c3bd2430d7b" : rpc error: code = Internal desc = failed to find disk on lun 0. azureDisk - findDiskByLun(0) failed with error(could not find disk id for lun: 0)
What you expected to happen:
provide the pvc to the pod
How to reproduce it:
try to attach an azuredisk to a windows kubernetes node of type
Standard_D4alds_v6
Anything else we need to know?:
Environment:
kubectl version
): v1.28.5The text was updated successfully, but these errors were encountered: