Bug 1629486

Summary: Crypto LUKS password not asked until after dropping to shell during boot
Product: [Fedora] Fedora Reporter: Barry Fishman <barry>
Component: dracutAssignee: dracut-maint-list
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: dracut-maint-list, jonathan, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-02 20:04:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
rdsosreport.txt described when boot failed to a shell prompt none

Description Barry Fishman 2018-09-16 19:37:21 UTC
Created attachment 1483777 [details]
rdsosreport.txt described when boot failed to a shell prompt

Description of problem:

I have a dual boot Fedora 28/ Windows 10 system using secure boot, with
encrypted / and swap partitions.  After initial install things worked fine,
but after I updated the kernel, booting results in timing out after 1min 30sec with:

dev/fedora_localhost-live/00 does not exist
/dev/fedora_localhost-live/01 does not exist
/dev/mapper/luks-88d4b669-f893-46e0-a1bb-64593e06465a does not exist
crypto LUKS UUID 88d4b669-f893-46e0-a1bb-64593e06465a not found
crypto LUKS UUID 3fddc8ec-abb1-4041-839c-ceb5291174ae  not found

And I am left a shell prompt.  When I exit the shell, it then asks me for the password, and the rest for the booting continues without further problems.

How reproducable:

Every time I select a kernel other than the one the system was first setup with.



Steps to Reproduce:
1. Boot the system
2. Select the latest kernel

Actual results:

As described above

Expected results:

To be prompted for the encryption password before mounts attempted

Additional info:

On a 6th Gen Lenovo X1 Carbon laptop.  Was setup by shrinking the Windows 10
system and installing in the resulting available space.

Comment 1 Ben Cotton 2019-05-02 19:22:16 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Barry Fishman 2019-05-02 20:04:09 UTC
I don't have a system to try a new encrypted boot, so since nobody else seems to have an issue I think its best to close this bug report.

Comment 3 Ben Cotton 2019-05-02 20:55:36 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.