@rbalint I've included the logs but I don't see any Traces as mentioned
in LP: #1824341
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1826916
Title:
MAAS unin
dpk logging from the same time period
** Attachment added: "unattended-upgrades-dpkg.log.1"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261356/+files/unattended-upgrades-dpkg.log.1
--
You received this bug notification because you are a member of Ubuntu
Touch see
requested logging during the month of the error
** Attachment added: "unattended-upgrades.log.1"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261355/+files/unattended-upgrades.log.1
--
You received this bug notification because you are a member of Ubuntu
Touch see
The machine I was using has been redeployed without LVM. If I get a
chance to redeploy I'll grab the requested logs. It's fairly trivial to
trigger if you have a machine available to deploy with lvm boot as
described above.
--
You received this bug notification because you are a member of Ubuntu
** Package changed: maas (Ubuntu) => maas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1573982
Title:
LVM boot problem - volumes not activated after upgrade to Xenial
Stat
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:
lv
6 matches
Mail list logo
