| 2015-10-24 21:18:08 |
MegaBrutal |
bug |
|
|
added bug |
| 2015-10-24 21:19:45 |
MegaBrutal |
bug task added |
|
lvm2 (Ubuntu) |
|
| 2015-10-24 21:20:16 |
MegaBrutal |
bug task added |
|
initramfs-tools (Ubuntu) |
|
| 2015-10-24 21:30:13 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2015-10-24 21:39:12 |
MegaBrutal |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2015-10-25 00:06:02 |
MegaBrutal |
tags |
|
regression-release wily |
|
| 2015-10-25 19:12:06 |
Julian Taylor |
bug |
|
|
added subscriber Julian Taylor |
| 2015-10-26 19:29:08 |
Andy Whitcroft |
initramfs-tools (Ubuntu): status |
New |
In Progress |
|
| 2015-10-26 19:29:11 |
Andy Whitcroft |
initramfs-tools (Ubuntu): importance |
Undecided |
High |
|
| 2015-10-26 19:29:14 |
Andy Whitcroft |
initramfs-tools (Ubuntu): assignee |
|
Andy Whitcroft (apw) |
|
| 2015-10-26 19:29:25 |
Andy Whitcroft |
initramfs-tools (Ubuntu): milestone |
|
ubuntu-15.11 |
|
| 2015-10-26 19:29:32 |
Andy Whitcroft |
lvm2 (Ubuntu): status |
New |
Invalid |
|
| 2015-10-26 19:29:35 |
Andy Whitcroft |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2015-10-26 19:34:10 |
Andy Whitcroft |
lvm2 (Ubuntu): status |
Invalid |
In Progress |
|
| 2015-10-26 19:34:13 |
Andy Whitcroft |
lvm2 (Ubuntu): importance |
Undecided |
High |
|
| 2015-10-26 19:34:16 |
Andy Whitcroft |
lvm2 (Ubuntu): assignee |
|
Andy Whitcroft (apw) |
|
| 2015-10-26 19:34:19 |
Andy Whitcroft |
lvm2 (Ubuntu): milestone |
|
ubuntu-15.11 |
|
| 2015-12-07 20:29:51 |
Andy Whitcroft |
lvm2 (Ubuntu): milestone |
ubuntu-15.11 |
ubuntu-15.12 |
|
| 2015-12-07 20:29:52 |
Andy Whitcroft |
initramfs-tools (Ubuntu): milestone |
ubuntu-15.11 |
ubuntu-15.12 |
|
| 2016-01-11 13:49:23 |
Thomas Johnson |
bug |
|
|
added subscriber Thomas Johnson |
| 2016-01-19 10:30:09 |
Andy Whitcroft |
lvm2 (Ubuntu): milestone |
ubuntu-15.12 |
ubuntu-16.01 |
|
| 2016-01-19 10:30:11 |
Andy Whitcroft |
initramfs-tools (Ubuntu): milestone |
ubuntu-15.12 |
ubuntu-16.01 |
|
| 2016-02-01 12:34:05 |
Andy Whitcroft |
lvm2 (Ubuntu): milestone |
ubuntu-16.01 |
ubuntu-16.02 |
|
| 2016-02-01 12:34:07 |
Andy Whitcroft |
initramfs-tools (Ubuntu): milestone |
ubuntu-16.01 |
ubuntu-16.02 |
|
| 2016-03-10 10:34:54 |
Andy Whitcroft |
lvm2 (Ubuntu): milestone |
ubuntu-16.02 |
ubuntu-16.03 |
|
| 2016-03-10 10:34:57 |
Andy Whitcroft |
initramfs-tools (Ubuntu): milestone |
ubuntu-16.02 |
ubuntu-16.03 |
|
| 2019-06-18 16:40:17 |
Chaskiel Grundman |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868268 |
|
| 2019-06-18 16:40:17 |
Chaskiel Grundman |
bug task added |
|
lvm2 (Debian) |
|
| 2019-06-18 22:44:23 |
Brian Murray |
tags |
regression-release wily |
regression-release rls-bb-incoming wily |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
lvm2 (Ubuntu Bionic) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
initramfs-tools (Ubuntu Bionic) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
lvm2 (Ubuntu Eoan) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
initramfs-tools (Ubuntu Eoan) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
nominated for series |
|
Ubuntu Disco |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
lvm2 (Ubuntu Disco) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
initramfs-tools (Ubuntu Disco) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
lvm2 (Ubuntu Cosmic) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
initramfs-tools (Ubuntu Cosmic) |
|
| 2019-06-20 15:39:35 |
Steve Langasek |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2019-06-20 15:40:57 |
Steve Langasek |
bug task deleted |
initramfs-tools (Ubuntu) |
|
|
| 2019-06-20 15:41:20 |
Steve Langasek |
bug task deleted |
initramfs-tools (Ubuntu Bionic) |
|
|
| 2019-06-20 15:41:27 |
Steve Langasek |
bug task deleted |
initramfs-tools (Ubuntu Cosmic) |
|
|
| 2019-06-20 15:41:32 |
Steve Langasek |
bug task deleted |
initramfs-tools (Ubuntu Disco) |
|
|
| 2019-06-20 15:41:38 |
Steve Langasek |
bug task deleted |
initramfs-tools (Ubuntu Eoan) |
|
|
| 2019-06-20 15:50:52 |
Brian Murray |
tags |
regression-release rls-bb-incoming wily |
regression-release wily |
|
| 2019-06-20 18:26:38 |
Brian Murray |
lvm2 (Ubuntu Eoan): milestone |
ubuntu-16.03 |
|
|
| 2019-06-20 18:26:38 |
Brian Murray |
lvm2 (Ubuntu Eoan): assignee |
Andy Whitcroft (apw) |
|
|
| 2019-06-21 12:26:27 |
Francis Ginther |
tags |
regression-release wily |
id-5d0ba914f340e31a8e9f2cf1 regression-release wily |
|
| 2019-06-22 19:04:50 |
Bug Watch Updater |
lvm2 (Debian): status |
Unknown |
Incomplete |
|
| 2019-07-24 21:21:05 |
Brad Figg |
tags |
id-5d0ba914f340e31a8e9f2cf1 regression-release wily |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release wily |
|
| 2019-11-22 21:58:47 |
Steve Langasek |
linux (Ubuntu Bionic): status |
New |
Invalid |
|
| 2019-11-22 22:00:52 |
Steve Langasek |
linux (Ubuntu Cosmic): status |
New |
Invalid |
|
| 2019-11-22 22:01:01 |
Steve Langasek |
linux (Ubuntu Disco): status |
New |
Invalid |
|
| 2019-11-22 22:01:14 |
Steve Langasek |
lvm2 (Ubuntu Cosmic): status |
New |
Won't Fix |
|
| 2019-11-22 22:03:20 |
Steve Langasek |
lvm2 (Ubuntu Eoan): status |
In Progress |
Triaged |
|
| 2019-11-24 02:18:48 |
Launchpad Janitor |
lvm2 (Ubuntu): status |
In Progress |
Fix Released |
|
| 2020-01-20 09:40:29 |
Julian Andres Klode |
lvm2 (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2020-01-22 15:12:45 |
Julian Andres Klode |
description |
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to VM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-01-23 15:45:54 |
Julian Andres Klode |
lvm2 (Ubuntu Eoan): status |
Triaged |
In Progress |
|
| 2020-01-23 15:45:59 |
Julian Andres Klode |
lvm2 (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-01-23 18:59:00 |
Łukasz Zemczak |
lvm2 (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-01-23 18:59:02 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-01-23 18:59:05 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-01-23 18:59:09 |
Łukasz Zemczak |
tags |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release wily |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release verification-needed verification-needed-eoan wily |
|
| 2020-01-23 19:00:49 |
Łukasz Zemczak |
lvm2 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-01-23 19:00:55 |
Łukasz Zemczak |
tags |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release verification-needed verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release verification-needed verification-needed-bionic verification-needed-eoan wily |
|
| 2020-01-23 19:10:54 |
Julian Andres Klode |
bug |
|
|
added subscriber Julian Andres Klode |
| 2020-01-23 23:30:45 |
eric porter |
removed subscriber eric porter |
|
|
|
| 2020-04-27 16:47:31 |
Brian Murray |
tags |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release verification-needed verification-needed-bionic verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release removal-candidate verification-needed verification-needed-bionic verification-needed-eoan wily |
|
| 2020-05-18 08:52:52 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to VM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-05-18 09:09:00 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Remove demsetup
3. Add second disk to it
4. Run pvcreate /dev/vdb
5. Run vgextend ubuntu-vg /dev/vdb
6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-05-18 09:09:54 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Remove demsetup
3. Add second disk to it
4. Run pvcreate /dev/vdb
5. Run vgextend ubuntu-vg /dev/vdb
6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove demsetup
Reboot and check that it fails to boot
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-05-18 09:15:46 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove demsetup
Reboot and check that it fails to boot
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove mdadm
Reboot and check that it fails to boot
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-05-18 09:18:34 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove mdadm
Reboot and check that it fails to boot
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove mdadm
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
8. Downgrade lvm2 to release
Reboot and check that it fails to boot
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2020-05-18 09:26:17 |
Julian Andres Klode |
tags |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release removal-candidate verification-needed verification-needed-bionic verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release removal-candidate verification-done-bionic verification-needed verification-needed-eoan wily |
|
| 2020-05-18 09:26:24 |
Julian Andres Klode |
tags |
cscc id-5d0ba914f340e31a8e9f2cf1 regression-release removal-candidate verification-done-bionic verification-needed verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf regression-release verification-done-bionic verification-needed verification-needed-eoan wily |
|
| 2020-05-18 12:54:41 |
Francis Ginther |
tags |
cscc id-5d0ba914f340e31a8e9f2cf regression-release verification-done-bionic verification-needed verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf id-5d0ba914f340e31a8e9f2cf1 regression-release verification-done-bionic verification-needed verification-needed-eoan wily |
|
| 2020-05-18 13:06:37 |
Julian Andres Klode |
tags |
cscc id-5d0ba914f340e31a8e9f2cf id-5d0ba914f340e31a8e9f2cf1 regression-release verification-done-bionic verification-needed verification-needed-eoan wily |
cscc id-5d0ba914f340e31a8e9f2cf id-5d0ba914f340e31a8e9f2cf1 regression-release verification-done verification-done-bionic verification-done-eoan wily |
|
| 2020-05-19 22:58:52 |
Launchpad Janitor |
lvm2 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-05-19 22:58:56 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-05-21 08:24:44 |
Launchpad Janitor |
lvm2 (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-05-22 13:32:48 |
Julian Andres Klode |
description |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
Reboot and check that it still boots.
6. Remove mdadm
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
8. Downgrade lvm2 to release
Reboot and check that it fails to boot
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv
Reboot and check that it still boots.
6. Remove mdadm
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
8. Downgrade lvm2 to release
Reboot and check that it fails to boot
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. |
|
| 2021-02-25 20:47:16 |
Bug Watch Updater |
lvm2 (Debian): status |
Incomplete |
Fix Released |
|
