Confirmed that the bug does not occur when increasing the size of the disk. Having a disk large enough triggers the creation of a crypto swap partition.
A crypto swap partition shows up as a type: dm_crypt device in the partitioning config. To determine if it needs to install cryptsetup, curtin checks for the presence of at least one "type: dm_crypt" device. Currently, this is only true if a crypto swap partition is present [1]. But it should be true when ZFS+encryption is used, irrelevant of the presence of a crypto swap. [1] https://github.com/canonical/curtin/blob/5fd4993b45cda829b41b1173237e36a8b405ba8d/curtin/block/deps.py#L67C1-L67C40 ** Changed in: curtin Status: New => Triaged ** Summary changed: - Target VM does not boot after installing with zfs+encryption + Fail to boot after installing using zfs+encryption on a small disk - cryptsetup not present in initramfs ** Summary changed: - Fail to boot after installing using zfs+encryption on a small disk - cryptsetup not present in initramfs + Failure to boot after installing using zfs+encryption on a small disk - cryptsetup not present in initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2119293 Title: Failure to boot after installing using zfs+encryption on a small disk - cryptsetup not present in initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/2119293/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
