Bug 1958438
| Summary: | indefinite wait at startup for non-configured cryptoLUKS device | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 34 | CC: | awilliam, bugzilla, dracut-maint-list, jonathan, robatino, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-07-03 19:51:31 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1891953 | ||||||
| Attachments: |
|
||||||
Proposed as a Blocker for 35-beta by Fedora user chrismurphy using the blocker tracking app because: If I have a cryptLUKS partition on the system at the time of a Fedora installation, and do an installation that doesn't include this partition and also doesn't use any encrypted devices at all, I get an unexpected passphrase dialog at the next boot that requires user intervention. Basic: "A system installed with a release-blocking desktop must boot to a log in screen. In all of the above cases, the boot should proceed without any unexpected user intervention being required. " It's the same dracut in F34 and Rawhide so I'm assuming the same bug exists in Rawhide. Someone will surely ask/test if this is still a bug once it really matters. from the upstream issue, you weren't able to reproduce this issue when you tried again. does it still seem to be a problem? I can't reproduce it anymore. |
Created attachment 1780918 [details] journal.log Description of problem: Following clean install of Fedora 34, a cryptoLUKS device is added. And now I get a plymouth dialog to unlock the device before I can startup. This is a device that was not configured at the time of Fedora 34 being installed, but its existence now prevents boot. It can also prevent boot following a clean install of Fedora 34 when that cryptoLUKS device was ignored (not included in the installation). Version-Release number of selected component (if applicable): dracut-053-5.fc34.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 34 no encryption. 2. Add a partition with a cryptoLUKS signature (cryptsetup luksFormat). 3. Boot Actual results: I get a plymouth passphrase screen, indefinite wait. Expected results: The system should boot. There's no rd.luks hint on the kernel command line, there's no /etc/crypttab configuration. It's asking for a passphrase for this device merely because it exists and isn't at all part of the boot chain. Additional info: