Description of problem: fedup 0.8 from F19 to F20 starts after rebooting, then stops after "Mounted /boot". Version-Release number of selected component (if applicable): 0.8 How reproducible: Always Steps to Reproduce: 1. Install F19 with / and /home encrypted with LUKS 2. Try to update to F20 using fedup --iso, with the appropriate --enablerepos to pull in Fedora 20 and Fedora 20 update repos, so that all dependencies get resolved with no failures. Actual results: fedup --iso completes without errors, reboot start after the "Mounted /boot" message. Expected results: Update starts, and runs. Additional info: systemctl list-jobs shows the following: 132 system-upgrade.target start waiting 133 sysinit.target start waiting 134 local-fs.target start waiting 135 home.mount start waiting 136 systemd-fsck@dev-map...x2d48f2\x2d9ad1\x2d49da41ccd72e.service start waiting 137 dev-mapper-luks\x2d6...\x2d48f2\x2d9ad1\x2d49da41ccd72e.device start running 138 systemd-cryptsetup@l...x2d48f2\x2d9ad1\x2d49da41ccd72e.service start running 166 systemd-journal-flush.service start waiting 174 systemd-tmpfiles-setup.service start waiting 184 plymouth-read-write.service start waiting 185 cryptsetup.target start waiting 194 system\x2dupgrade-media.mount start waiting 195 upgrade-prep.service start waiting 200 systemd-readahead-done.timer start waiting This appears to be the prompt to unlock a LUKS partition. The reboot prompted me once, for /'s password. I was not prompted for /home's password. Both partitions have the same LUKS password. Early versions of LUKS support in Fedora prompted me separately for each partition, at system boot. Several releases ago, Fedora started prompting me only once for the LUKS password, and automatically tried it with the second partition. Here, I get only one password prompt.
The temporary workaround appears to be to switch to ALT-F2, and run systemctl cancel, on those stuck jobs. The main VT then complains loudly about /home, then continues to upgrade the system.
Had more time to look at what happened during this upgrade. It appears that using systemctl cancel to kill the hanging password prompts to unlock unneeded partitions, and resume the upgrade, worked with no apparent ill effects. The upgraded F20 is perfectly healthy.
I have the same problem on my thinkpad with / and /home encrypted. But yesterday I updated my PC from F19 to F20 without any issues. And it has / and /home encrypted too.
The problem is very likely that the system is trying to unlock /home, but SELinux is preventing systemd-tty-ask-password-agent from reading the (saved) password you used to unlock /. This only happens if / and /home are *separate* LUKS partitions. If they're the same LUKS volume it'll work fine. Does it work if you add "enforcing=0" to the boot arguments?
*** Bug 1046281 has been marked as a duplicate of this bug. ***
I have just updated my laptop without any issues after adding "enforcing=0" to boot arguments.
*** Bug 1044761 has been marked as a duplicate of this bug. ***
I can confirm both the problem and the workaround described in Comment 6.
*** Bug 1044551 has been marked as a duplicate of this bug. ***
"enforcing=0" works it around for me as well. Please be sure to document this bug and the workaround in <https://fedoraproject.org/wiki/Common_F20_bugs#Upgrade_issues> -- Fedora 19 will reach end of life in less than two weeks, and likely many people will be triggered to upgrade. (I'm upgrading an F19 laptop in the family only because F19 is reaching EOL.) FedUp version I'm using: fedup-0.9.1-1.fc19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.