I have used the "cryptsetup luksOpen` work-around successfully already
years ago.

However, when installing 20.04 with the server installer it does no longer work.
Installation aborts; in the log I found the cause to be

   raise ValueError("encryption key or keyfile must be specified")

from

https://github.com/canonical/curtin/blob/45877d0e1f5774dc424f73b0c1c16b65e0353e63/curtin/commands/block_meta.py#L1394

(Note: This is not necessary the commit that was in use when I used the
installer. I just looked at the current master branch to point to the
message I got. I did upload the crash report, but I don't have a link to
my upload.)

Obviously the installer got confused ny the work-around because it
noticed that there is a LUKS container, but it had never gotten any
secret related to it.

Is there more than one Server installer, that could explain the
discrepancy against the instructions above?

I tried the xubuntu-20.04.2.0 and there the work-around still works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904270

Title:
  ubiquity does not support existing LUKS encrypted partitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1904270/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to