Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Kickstarting RHEL8.5 with the following partitioning, it fails to prompt for luks passphrase at boot.
This worked previously on RHEL8.2 with plymouth plymouth-0.9.3-16.el8.x86_64 and downgrading to that version after installation also works.
Any later version of plymouth (& plymouth-core-libs) and it fails to boot, no prompt is issued.
Version-Release number of selected component (if applicable):
plymouth-0.9.4-7.20200615git1e36e30.el8.x86_64 or later
How reproducible:
Always
Steps to Reproduce:
1. kickstart RHEL8.5 with this partitioning
part / --fsoptions="noatime" --size=4096
part /boot --size=1024
part pv.01 --ondisk=sda --size=1024 --grow
volgroup vg01 --pesize=4096 pv.01
part pv.02 --ondisk=sdb --size=1024 --grow --encrypted --passphrase=testing
volgroup vg02 --pesize=4096 pv.02
logvol /var --fsoptions="noatime" --vgname=vg01 --size=1024 --name=var
logvol /tmp --vgname=vg01 --size=1024 --name=tmp
logvol swap --vgname=vg01 --size=1024 --name=swap
logvol /cache/disk-01 --vgname=vg02 --size=6144 --name=cache01
Actual results:
boot hangs, no prompt for passphrase is displayed
Expected results:
prompt for passphrase
Additional info:
Tested and this is the same for any version of plymouth later than plymouth-0.9.3-16.el8.x86_64 in RHEL8 and also the same for RHEL9 beta
If you add a passphrase for pv.01 then prompts for both pv.01 and pv.02 appear
Comment 3Ray Strode [halfline]
2022-02-21 12:16:07 UTC
do you have access to serial console? if so can you put
plymouth.debug=stream:/dev/kmsg printk.devkmsg=on
on kernel command line and post output?
Comment 5Ray Strode [halfline]
2022-02-21 16:29:12 UTC
hmm for some reason the fd for `/dev/kmsg` hung up, preventing further logging from going through
[couldn't write a log entry: Invalid argument]
. I guess the fd got closed somehow, not sure.
Can you try changing the the
plymouth.debug=stream:/dev/kmsg
to just
plymouth.debug
and see if that gets us the messages we need?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (plymouth bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1965