What were you trying to do that didn't work?

In ARM VM on Azure, if has multiple disks, there's one disk symlink missing in /dev/disk/by-path. Such as, the os disk is sdb. Check /dev/disk/by-path:
lrwxrwxrwx. 1 root root  9 Dec  4 09:57 acpi-MSFT1000:00-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part3 -> ../../sdb3
Then attach one datadisk sda, the sdb symlink is covered:
lrwxrwxrwx. 1 root root  9 Dec  4 09:58 acpi-MSFT1000:00-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part3 -> ../../sdb3
 

Not see it in x86_64:
[root@LISAv2-walaauto240-IY52-1204171809-role-0 ~]# ll /dev/disk/by-path
lrwxrwxrwx. 1 root root  9 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-0 -> ../../sdb
lrwxrwxrwx. 1 root root 10 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-0-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-0-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root 10 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-0-part3 -> ../../sdb3
lrwxrwxrwx. 1 root root 10 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-0-part4 -> ../../sdb4
lrwxrwxrwx. 1 root root  9 Dec  4 10:07 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-1 -> ../../sdc
lrwxrwxrwx. 1 root root 10 Dec  4 10:07 acpi-VMBUS:00-vmbus-f8b3781a1e824818a1c363d806ec15bb-lun-1-part1 -> ../../sdc1
lrwxrwxrwx. 1 root root  9 Dec  4 10:06 acpi-VMBUS:00-vmbus-f8b3781b1e824818a1c363d806ec15bb-lun-0 -> ../../sda

Please provide the package NVR for which the bug is seen:

kernel-5.14.0-536.el9.aarch64
systemd-udev-252-48.el9.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

1.  Create a VM on Azure in Standard_D2ps_v5/v6 size. Check /dev/disk/by-path
2.  Attach one datadisk, then check /dev/disk/by-path again

Expected results

All the disk symlinks should exist in /dev/disk/by-path. Such as:
lrwxrwxrwx. 1 root root  9 Dec  4 09:58 acpi-MSFT1000:00-scsi-xxx -> ../../sda
lrwxrwxrwx. 1 root root  9 Dec  4 09:58 acpi-MSFT1000:00-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part3 -> ../../sdb3

Actual results

The os disk symlink is covered by the datadisk symlink:
lrwxrwxrwx. 1 root root  9 Dec  4 09:58 acpi-MSFT1000:00-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root 10 Dec  4 09:48 acpi-MSFT1000:00-scsi-0:0:0:0-part3 -> ../../sdb3