[BUG] Azure D-v6 series node pool instance fail to mount persistent volume in AKS

[prashantp48]

Describe the bug
AKS node pools having instance Dv6 series fails for the pods using persistent volume, giving error
MountVolume.MountDevice failed for volume "pvc-67d71c1a-e9c2-4b0c-9abd-a20f9afb9d06" : rpc error: code = Internal desc = failed to find disk on lun 0. azureDisk - findDiskByLun(0) failed with error(failed to find disk by lun 0)

To Reproduce
Steps to reproduce the behavior:

1. Create a node pool with D4as_V6 instance or any v6 instance.
2. Deploy a pod which uses persistent volume like redis.
3. Pod will not start and stuck in init:0/1 state.

Expected behavior
Pod should be in running state.

Screenshots

Environment (please complete the following information):

• CLI Version: v1.29.3
• Kubernetes version 1.28.9

Additional context
Events:
Type Reason Age From Message

---

Normal Scheduled 116s default-scheduler Successfully assigned hypexe-controlpane-nonprod-sc/hypex-redis-master-0 to aks-utility0406-23602633-vmss000004
Warning FailedMount 41s (x8 over 113s) kubelet MountVolume.MountDevice failed for volume "pvc-67d71c1a-e9c2-4b0c-9abd-a20f9afb9d06" : rpc error: code = Internal desc = failed to find disk on lun 0. azureDisk - findDiskByLun(0) failed with error(failed to find disk by lun 0)

[andyzhangx]

pls follow this guide to use the workaround: kubernetes-sigs/azuredisk-csi-driver#2777 (comment), the aks rp fix would rollout in Feb.