Bug 1066121
| Summary: | Unlocking my root volume fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Strauss <david> | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | agk, david, dwysocha, extras-orphan, gmazyland, johannbg, lnykryn, msekleta, okozina, pjones, plautrba, prockai, rvokal, systemd-maint, vpavlin, whulbert, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-29 15:15:47 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: |
|
||||||
This looks like some magic have broken between plymouth and systemd (+systemd-cryptsetup). (Cryptsetup is here related indirectly through libcryptsetup/systemd-cryptsetup... so I think primarily it is problem there...) I hope someone from systemd camp can help to debug this better. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 864229 [details] LUKS fails to unlock Description of problem: After rebooting, I get the LUKS unlock password prompt, enter the password, and then see a the Fedora boot progress dialog keep creeping along but never finishing. If I press Esc, I see the system repeatedly trying to set up LUKS (as shown in attachment). Version-Release number of selected component (if applicable): Name : cryptsetup Arch : x86_64 Version : 1.6.3 Release : 1.fc20 How reproducible: Happens every time I reboot, especially if I wait a bit to enter the password. If I reboot again and enter the password immediately, things seem to come up fine. Steps to Reproduce: 1. Install Fedora with a LUKS-encrypted root volume. 2. Reboot. 3. Try to unlock the volume.