[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-12 Thread Launchpad Bug Tracker
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu3.18.04.2 --- lvm2 (2.02.176-4.1ubuntu3.18.04.2) bionic; urgency=medium * d/p/fix-auto-activation-at-boot.patch: (LP: #1854981) Allow LV auto-activation (e.g. /usr on it's separate LV) -- Eric Desrochers Thu, 05 Dec

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-12 Thread Launchpad Bug Tracker
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu4.2 --- lvm2 (2.02.176-4.1ubuntu4.2) disco; urgency=medium * d/p/fix-auto-activation-at-boot.patch: (LP: #1854981) Allow LV auto-activation (e.g. /usr on it's separate LV) -- Eric Desrochers Thu, 05 Dec 2019

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-06 Thread Eric Desrochers
[VERIFICATION DISCO] I have installed Disco, layout /usr on it's on LV, and at reboot same problem as describe in the impact section. Server stuck in trying to mount /usr due to lack of LVM activation. At the initramfs prompt, I ran 'lvm vgchange -ay' to boot properly. I installed the

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-06 Thread Eric Desrochers
I have restart the autopkgtest and they all passes BUT the disco cinder ones. Looking at the failure, it's not related to this current SRU, and it seems to be a recurrent failing pattern: autopkgtest [04:07:34]: test cinder-daemons: [--- 2019-12-06 04:07:37.800 12844 WARNING

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-06 Thread Eric Desrochers
I have restart the autopkgtest and they all passes BUT the disco cinder ones. Looking at the failure, it's not related to this current SRU, and it seems to be a recurrent failing pattern: autopkgtest [04:07:34]: test cinder-daemons: [--- 2019-12-06 04:07:37.800 12844 WARNING

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-06 Thread Eric Desrochers
[VERIFICATION BIONIC] I have installed Bionic, layout /usr on it's on LV, and at reboot same problem as describe in the impact section. Server stuck in trying to mount /usr due to lack of LVM activation. At the initramfs prompt, I ran 'lvm vgchange -ay' to boot properly. I installed the

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Description changed: [Impact] In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM activation doesn't occurs during the boot process (except for LVM root partition) and since /usr is an important component before the 'pivot'[0], the init inside the initramfs space

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Łukasz Zemczak
Hello Eric, or anyone else affected, Accepted lvm2 into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Changed in: lvm2 (Ubuntu Xenial) Status: Won't Fix => Fix Released -- 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/1854981 Title: system doesn't properly boot as

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Description changed: [Impact] In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM activation doesn't occurs during the boot process (except for LVM root partition) and since /usr is an important component before the 'pivot'[0], the init inside the initramfs space

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
Uploaded in B/D. Waiting for SRU team verification team to approve and allow packages to start building in -proposed. - Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Changed in: lvm2 (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: lvm2 (Ubuntu Disco) Status: Confirmed => In Progress ** Changed in: lvm2 (Ubuntu Disco) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: lvm2 (Ubuntu Bionic) Assignee:

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Description changed: + ## DRAFT in progress ## + + [Impact] + In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM activation doesn't occurs during the boot process (except for LVM root partition) and since /usr is an important component before the 'pivot'[0], the

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Changed in: lvm2 (Ubuntu Xenial) Status: New => Won't Fix -- 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/1854981 Title: system doesn't properly boot as expected if

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-05 Thread Eric Desrochers
** Also affects: lvm2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: initramfs-tools

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-04 Thread Eric Desrochers
The problem seems to come from "/udev/69-dm-lvm-metad.rules.in". Still investigating, stay tuned. -- 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/1854981 Title: system

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
I wonder if this behaviour is not observe in Eoan because it is the first Ubuntu release introducing the removal of lvmetad[0] (starting v2_03_00) in favour of 'event_activation'[1] (starting v2_03_03) in lvm2. Seems like a lot happened between lvm2 found in disco and eoan in term of development

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
I wonder if this behaviour is not observe in Eoan because it is the first Ubuntu release introducing the removal of lvmetad[0] (starting v2_03_00) in favour of 'event_activation'[1] (starting v2_03_03) in lvm2. Seems like a lot happened between lvm2 found in disco and eoan in term of development

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
** Description changed: Only the lv for root volume get activated, because of the grub parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv" http://man7.org/linux/man-pages/man7/bootparam.7.html 'root=...'   This argument tells the kernel what device

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
** Description changed: Only the lv for root volume get activated, because of the grub parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv" http://man7.org/linux/man-pages/man7/bootparam.7.html 'root=...'   This argument tells the kernel what device

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
** Changed in: lvm2 (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Description changed: Only the lv for root volume get activated, because of the grub parameter that specifies/enforce it

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
** Description changed: - Only the lv for root volume get activated, most likely because of the - grub parameter that specifies it "root=/dev/mapper/ubuntu-vg-ubuntu--lv" + Only the lv for root volume get activated, because of the grub parameter + that specifies/enforce it

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
initramfs.debug_DISCO ** Attachment added: "initramfs.debug_DISCO" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854981/+attachment/5309607/+files/initramfs.debug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

2019-12-03 Thread Eric Desrochers
For context about the /usr merge: https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ https://wiki.debian.org/UsrMerge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.