I've run across this today and it affects MAAS.
MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)
Configuring an LVM based drive with a raid on top of it for the root
partition will trigger this. Deploying the default kernel / OS will fail
due to inactive volume groups.
The fix as expected:
lvm vgchange -ay
mdadm --assemble --scan
exit
Then apply the above mentioned script to make it stick.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573982
Title:
LVM boot problem - volumes not activated after upgrade to Xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
