The risk here, especially with physical systems, is that the path (/dev/sda) is not reliable. That is, from boot to boot, the path to a specific disk may differ (sda may point to a different physical device).
MAAS certainly knows (physical system) or can construct (virtual) disks with serial numbers to ensure consistent and reliable deployments.
I would suggest this is not a bug, but rather configuration error (missing serial number in disk config).
Why do the disks on physical or virtual not have a serial number?
Looking at the physical logs, they certainly do have serial numbers.
2021-04- 24T01:12: 48-05:00 dell2 cloud-init[1606]: get_path_ to_storage_ volume for volume sda 24T01:12: 48-05:00 dell2 cloud-init[1606]: Processing serial 6842b2b01b006d0 024858f55183677 de via udev to 6842b2b01b006d0 024858f55183677 de 24T01:12: 48-05:00 dell2 cloud-init[1606]: lookup_disks found: ['wwn-0x6842b2b 01b006d0024858f 55183677de' , 'scsi-36842b2b0 1b006d0024858f5 5183677de' , 'wwn-0x6842b2b0 1b006d0024858f5 5183677de- part1', 'scsi-36842b2b0 1b006d0024858f5 5183677de- part1'] 24T01:12: 48-05:00 dell2 cloud-init[1606]: lookup_disks realpath( wwn-0x6842b2b01 b006d0024858f55 183677de) =/dev/sda
2021-04-
2021-04-
2021-04-
Is it not included in your custom storage config? No serial numbers in the config.
> Here is the proposed change. /pastebin. ubuntu. com/p/cvNd4Kbck y/
> https:/
The risk here, especially with physical systems, is that the path (/dev/sda) is not reliable. That is, from boot to boot, the path to a specific disk may differ (sda may point to a different physical device).
MAAS certainly knows (physical system) or can construct (virtual) disks with serial numbers to ensure consistent and reliable deployments.
I would suggest this is not a bug, but rather configuration error (missing serial number in disk config).