When obtaining unique ids for identifying a block storage
device, block-discover looks for ID_WWN and ID_SERIAL values
and will use them in the rendered storage config. In some cases
the value of these attributes may be invalid. For example, some
consumer disks might have an invalid WWN number:
0x00000000000000000000
Curtin will also ingnore empty values, like
ID_SERIAL=' '
Excluded ids will not be emitted in the final storage config.
vmtest: rsync don't cross filesystem boundaries when copying
In some scenarios /var/lib/lxcfs is mounted with kernel bits
and rsync complains; instead we now copy using the --one-file-system
flag which avoids crossing these boundaries.
multipath: attempt to enforce /dev/mapper/mpath files are symlinks
Multipath device scanning and bring up variablity may result in
the creation of /dev/mapper/mpath* files that are block devices
instead of a symlink to the device mapper device (/dev/dm-0).
When these block files are present, this breaks assumptions in
curtin used to look up details in sysfs for a mapper device.
block-meta: device mapper partitions may be block devices not links
In some cases the multipath library may create a block device which
is not a symbolic link to the device-mapper dev[1]. Curtin expects the
symlink. Remove the non-symlink file and allow kpartx to create it.
Default to dm_name being id if empty earlier in dm_crypt_handler()
In other parts of the code, when deciding the path for dmcrypt_dev,
we default to 'id' when 'dm_name' is not defined. We ideally want
that to happen in all the cases. The defaulting has been there
already but a bit too late.
