activate_volgroup issues the vgchange --activate=y
command which will activate any known VolumeGroup and
any LogicalVolume defined within the VolumeGroup
The vgchange command itself handles syncing with udev
so there is no need to issue udevadm settle calls.
The lvm_scan changes which incorporated an automatic
activation are pulled out restoring the previous
behavior of just scanning and updating lvmetad
(if running) and the kernel.
clear-holders will now start a scan and issue
and activate explicity.
Refactor lvm_scan to handle precise/trusty lack of lvmetad
Turns out that while Trusty lvm has support for lvmetad, it's not
packaged. This prevents the pvscan --cache --activate=ay from
working as it does in Xenial and newer. On precise, trusty instead
we run the pvscan and vgscan, and then invoke vgchange --activate=ay
to enable any vgs and lvs the scans found.
Other changes:
- Use release to append vgchange cmd as needed
- Drop release check for use of --cache, param is required if
it is running
- Update unittest to match change in code
clear-holders: rescan for lvm devices after assembling raid arrays
Lvm devices to be found after assembling raid arrays. Add a call to lvm_scan
and update the pvscan call to use --activate ay which activates any found
vgs/lvs.
block: use uuid4 (random) when autogenerating UUIDS for filesystems
The use of uuid1 (timebased) results in UUID values that are visually
hard to distingish. Instead use uuid4 which generates a random
UUID value to provide a more visually distinctive /etc/fstab.
Updated tools/xkvm to add a virtio-rng device when launching VMs
I believe that this change removes the final 2G root (/) filesystems.
These 2G filesystems were too small to handle upgrades sometimes.
Things that lead to this state:
a.) we started testing with propsed enabled (and upgrade to it)
b.) the failing cases here were Trusty HWE tests, which end up
getting 2 kernels installed and 2 update-initramfs and such.
That worst case scenario led to the following output of apt:
Need to get 2404 kB of archives.
After this operation, 10.9 MB of additional disk space will be used.
Need to get 1467 kB of archives.
After this operation, 4904 kB of additional disk space will be used.
Need to get 68.3 MB of archives.
After this operation, 308 MB of additional disk space will be used.
Need to get 63.9 MB of archives.
After this operation, 275 MB of additional disk space will be used.
