| Summary: | Upgrading from Fedora 24 to Fedora 25 Beta on Btrfs LUKS no longer asks for passphrase | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Will Johansson <will.johansson> | ||||
| Component: | plymouth | Assignee: | dracut-maint-list | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | dracut-maint-list, elad, fedora, harald, jonathan, rstrode, 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: | 2017-12-12 10:52:39 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: | |||||
| Attachments: |
|
||||||
|
Description
Will Johansson
2016-10-20 17:51:10 UTC
How did you perform the upgrade? Without that info, it's hard to say anything. Anaconda is not involved during upgrades. So there's no "anaconda passphrase program" expected. Maybe the password prompt just got obscured by other stuff written to the console? Can you attach the logs from the boot? I mentioned upgrading via the dnf system upgrade plugin. # dnf system-upgrade download --refresh --releasever=25 # dnf system-upgrade reboot Sorry -- I thought anaconda was involved with asking for the LUKS passphrase at bootup. Is it just a dracut plugin for LUKS? Either way, that's possible. What's the best way to get the logs from the boot when the password prompt gets obscured? If it gets obscured, I can try typing the password after some delay and see if it gets in. Augh, it as plymouth I was thinking about, not anaconda. :) Sorry for the confusion. However, I did find this in the logs: Oct 20 10:23:11 london.europa systemd-tty-ask-password-agent[465]: Invalid password file /run/systemd/ask-password/ask.lYZXw8 Oct 20 10:23:11 london.europa systemd-tty-ask-password-agent[465]: Failed to show password: Bad message Hmm, that apparently is from the last successful boot with removing rhgb/quiet, rather than the failed boot with rhgb/quiet. Sorry. Let me try the dracut shell then and see if I can dump the log somewhere. So I booted with plymouth:debug also and I'm seeing errors. I'm seeing lots of bad file descriptors. Perhaps it's more plymouth that's the problem? I will attach the logs from plymouth. I'm happy to change the component to plymouth. That'd actually make sense. It didn't register to me that the standard textual progress bar came up at all either, but perhaps because that usually comes after the password input? Created attachment 1212694 [details]
Logs from plymouth, from using kernel argument "plymouth:debug"
FWIW, this plymouth is Version : 0.9.3 Release : 0.6.20160620git0e65b86c.fc25 for plymouth, plymouth-core, plymouth-scripts. If it works with "rd.plymouth=0" on the kernel cmdline, then it might be a plymouth bug. or "plymouth.enable=0" This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |