1) There are no changes with the cryptsetup in bionic-updates. This is expected, because the changes in initramfs-tools are gated by a file introduced in the patched cryptsetup.
Thus no regression from the initramfs-tools side. ... And, additional testing with the _patched_ cryptsetup, just in case so that we've it tested if/when it lands. 2) It works correctly with the patched crypsetup from PPA. This validates that the changes in initramfs-tools work as intended when paired with the new cryptsetup changes. 2.1) There are no changes in the good path/case i.e., RAID is not degraded, user enters correct password. 2.2) There is one more iteration to ask password 3 times. i.e., RAID is not degraded, user enters incorrect passwords. - original behavior: 2x iterations of asking password 3 times - modified behavior: 3x iterations of asking password 3 times 2.3) It can boot in the bad path/case i.e., RAID is degraded, user now can enter password and boot. - original behavior: times out in 180 seconds in local-top, checking LVM every 10 seconds, then drops to shell. - modified behavior: times out in 5 seconds in local-top, moves on to local-block, checks for 30 seconds every 1 second (including LVM); md/raid activated in 20 seconds. (asked for password and booted successfully.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
