← Back to team overview

ubuntu-public-cloud team mailing list archive

[Bug 2120745] Re: symlink failures for SCSI data disks on Azure (25.04)

 

** Also affects: azure-vm-utils (Ubuntu Questing)
   Importance: Undecided
       Status: New

** No longer affects: azure-vm-utils (Ubuntu Questing)

** Also affects: azure-vm-utils (Ubuntu Plucky)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Public Cloud, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2120745

Title:
  symlink failures for SCSI data disks on Azure (25.04)

Status in azure-vm-utils package in Ubuntu:
  New
Status in azure-vm-utils source package in Plucky:
  New

Bug description:
  My tests hit some unexpected failures with the labeling of SCSI data
  disks on 25.04.

  If a VM has say four data disks, with lun = 0, 1, 2, 3. We should also
  see /dev/disk/azure/data/by-lun/{0,1,2,3} for both NVMe and SCSI
  scenarios.    Tests show this working correctly for NVMe but SCSI
  disks were missing.

  I haven't root caused it yet, but it looks like udevadm test outputs
  aren't aligning with the actual outputs.

  $ disk=$(readlink -f /dev/disk/azure/scsi1/lun0)
  $ sudo udevadm test $disk 2>/dev/null| grep AZURE_DISK_TYPE
    AZURE_DISK_TYPE=data
  $ sudo udevadm info $disk | grep AZURE_DISK_TYPE
  $

  I would guess the initramfs was missing rules, but that's not the case
  here (and it is initrdless boot).

  I've not seen this issue with other images (22.04, 24.04) or latest
  Debian?

  To reproduce, create Ubuntu 25.04 VM on Azure with multiple data disks
  (in my case, 4 of them with luns 0-3), install azure-vm-utils and
  verify that /dev/disk/azure/data/by-lun/{1,2,3,4} is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/azure-vm-utils/+bug/2120745/+subscriptions



References