-
Notifications
You must be signed in to change notification settings - Fork 194
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
The nvme disk mount failure with azureDisk - findDiskByLun(0) failed with error(failed to find disk by lun 0) #2777
Comments
it's missing udev rules for nvme controller disks on the node, could you run following command, and then try again?
|
Yes, it works when I added the 80-azure-disk.rules! |
One more question, should CSI Driver cover this or does it need to be handled by node os part? |
we have set up this new udev rules in the new aks vhh image, it would rollout in aks rp 2025.2 release. |
o, you are using OpenShift, so I think you should include it in your image by yourself. here is an example PR: Azure/AgentBaker#5444 |
Yeah acked, thanks for the confirmation. |
What happened:
Azure disk mount failed on some instance types with error:
azureDisk - findDiskByLun(0) failed with error(failed to find disk by lun 0)
in Openshift, currently found the following:Standard_M16bds_v3
Standard_L8s_v4
Standard_M16bs_v3
When checking the node, seems there is no lun info (not sure if it is the reason):
What you expected to happen:
The disk should be mounted successfully
How to reproduce it:
Always
Anything else we need to know?:
Environment:
kubectl version
): v1.31.3uname -a
):The text was updated successfully, but these errors were encountered: