Issue #321: rhbz#1946074 boot failure when LV is a cryptoluks device used as sysroot - blocker-review

fedora-qa / blocker-review

#321 rhbz#1946074 boot failure when LV is a cryptoluks device used as sysroot

Closed 2 years ago by blockerbot. Opened 3 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1946074
Information from BlockerBugs App:

Current vote summary

Accepted FinalBlocker (+2, 0, -0)
- +1 by adamwill, chrismurphy

Commented but haven't voted yet: coremodule, geraldosimiao

The votes have been last counted at 2021-04-06 23:25 UTC and the last processed comment was #comment-725698

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)

adamwill commented 3 years ago

If this is as simple as 'go to custom partitioning and check an encrypt-this-thing box', I'm:
FinalBlocker +1

chrismurphy commented 3 years ago

It's that simple. But also if you have that same configuration made from F32 or F33 Custom installation, and do an upgrade to F34 getting dracut-34 it'll also fail to boot at some point (I'm not sure if during system upgrade dracut is always update before the kernel, or if it's possible the new f34 kernel has its initramfs made by f33 dracut).
FinalBlocker +1

coremodule commented 3 years ago

AGREED AcceptedFinalBlocker

Discussed during the 2021-04-05 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:

"The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration"

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-04-05/f34-blocker-review.2021-04-05-16.02.txt