Add the azure-vm-utils package to support Azure NVMe Disks

[marmijo]

Add the azure-vm-utils package to include udev rules to support certain VM types (e.g. Standard_M16bds_v3, Standard_M16bs_v3, Standard_L8s_v4) that present managed disks as NVMe devices instead of traditional SCSI disks. Without these rules, LUN-based disk detection fails in the Azure Disk CSI driver, causing volume mount failures.

Add the azure provided udev rules[1] through the azure-vm-utils package. This package was recently built for Fedora 41, so let's also fast-track it in testing-devel to start consuming it sooner.

[1]: https://github.com/Azure/azure-vm-utils/blob/6fb0ae1d047c0f06e19aab8f1e27e2cd588a6f9f/udev/80-azure-disk.rules

[dustymabe]

Thanks for working on this..

Were we able to reproduce the error case and verify adding the rules here fixes it?

[marmijo]

Were we able to reproduce the error case and verify adding the rules here fixes it?

I wasn't able to reproduce the exact issue, but I think I can confirm this fixes it. The issue is related to the Azure Disk CSI Driver not being able to perform LUN-based disk discovery without these udev rules. see: kubernetes-sigs/azuredisk-csi-driver#2777

I was able to confirm that the udev rules properly map NVMe devices in /dev/disk/azure and also sets AZURE_DISK_TYPE and AZURE_DISK_LUN to their proper values. These values are not set without the udev rules.

[core@marmijo-Standard_M16bds_v3 ~]$ udevadm info /dev/nvme0n2
M: nvme0n2
...
... (output truncated)
...
E: AZURE_DISK_TYPE=data
E: AZURE_DISK_LUN=0

[dustymabe]

I was able to confirm that the udev rules properly map NVMe devices in /dev/disk/azure and also sets AZURE_DISK_TYPE and AZURE_DISK_LUN to their proper values. These values are not set without the udev rules.

IOW we have enough to write a simple test for this?

[marmijo]

IOW we have enough to write a simple test for this?

Looks like it! 👍

[dustymabe]

LGTM