Description of problem: Upgrade from f18 to f19 using fedup. After rebooting, system-upgrade fails to start the upgrade process. Version-Release number of selected component (if applicable): f19 release How reproducible: always Steps to Reproduce: 1. Prepare with fedup # fedup --network 19 Finished properly, adding grub menu. 2. Reboot system and selected system-upgrade from GRUB menu 3. Upgrade fails to start. Actual results: The gui progressbar goes till end and then stops. When going to the text screen with 'Esc' see the following: ------------------- dracut-initqueue[358]: Failed to issue method call: Unit systemd-cryptsetup@luks\x2d1111...1111.service failed to load: No such file or directory. See system logs and 'systemctl statussystemd-cryptsetup@luks\x2d1111...1111.service' for details. dracut-initqueue[358]: Failed to issue method call: Unit systemd-cryptsetup@luks\x2d2222...2222.service failed to load: No such file or directory. See system logs and 'systemctl statussystemd-cryptsetup@luks\x2d2222...2222.service' for details. [...] dracut-initqueue[358]: rm: cannot remove '/lib/dracut/hooks/initqueue/timeout/resume.sh': No such file or directory dracut-initqueue[358]: rm: cannot remove '/lib/dracut/hooks/initqueue/settled/resume.sh': No such file or directory [...] [123.4567] systemd-cryptsetup-generator[2134]: Unknown kernelswitch rd.luks.key.tout=5. Ignoring. ------------------- LUKS password is not requested. Expected results: 1. LUKS password should be teken from the storage device or requested 2. LUKS partitions should be mounted as needed 3. Upgrade should start. Additional info: 1. In the system there are 2 LUKS partitions (home and swap). Their UUIDs are seen in the log as @luks\x2d1111...1111 and @luks\x2d2222...2222. 2. The grub cmdline contains their UUIDs as well as rd.luks.key= and rd.luks.key.tout= (sine f18 the latest is covered by https://bugzilla.redhat.com/show_bug.cgi?id=905683 so the workaround https://bugzilla.redhat.com/show_bug.cgi?id=905683#c1 was in place when doing fedup) 3. The SD card with LUKS key is in the slot
Small update: # fedup-cli --network 19 was used. And the 'rd.luks.uuid=' grub entry contains only beginning of the UUID, not the whole number (which is ok from dracut point of view to start f18).
Responding to myself: 1. In opposite to f18, the fedup upgrade to f19 and the f19 needs FULL uuid string in grub entry, not just its unique beginning. With this the upgrade continues. 2. Since then, after reboot, the f19 does not start saying stopping at: "Reached target Basic System." 3. Hopefully rebotting to rescue image starts the system. 4. In the dracut log it can be seen that the rescue image was created with lot of modules, however the initramfs-3.9.8-300.fc19.x86_64.img was created missing 'dm' and 'crypt' modules. 5. So create initramfs with missing modules: dracut -f /boot/initramfs-3.9.8-300.fc19.x86_64.img 3.9.8-300.fc19.x86_64 6. Reboot and it starts. 7. Reading key from storage is still broken (https://bugzilla.redhat.com/show_bug.cgi?id=905683)
This is the same problem as bug 974000. (In reply to prudy from comment #2) > Responding to myself: > 1. In opposite to f18, the fedup upgrade to f19 and the f19 needs FULL uuid > string in grub entry, not just its unique beginning. > > With this the upgrade continues. You need to fix this in your *existing* F18 entry in your bootloader config, or it won't get used by the F19 kernel when it's installed. > 2. Since then, after reboot, the f19 does not start saying stopping at: > "Reached target Basic System." Right - because your F18 boot config didn't have the arguments F19 needs, you've ended up with a F19 initrd that can't boot. Repeating for emphasis: this has to be fixed in the *existing F18 bootloader config*. One question remains - what was your 'rd.luks.uuid' entry before, and what did you change it to to make it work?
Well, grub entry for f18 with just beginning of uuid was explicitly valid and handled by dracut 90crypt/ scripts, and that was done on purpose especially to avoid typing long numbers. So what is needed now is not a fix, it's just f19 is not backward compatible. I could solve it for myself, but giving an upgrade tool you should not expect such actions from standard desktop users. Anyway, original f18 grub entry was: rd.luks.uuid=57af8 now it has to be all of it: rd.luks.uuid=57af8f53-0de0-4e88-975e-d859de918ca8
Sorry, typo, this is copy-paste from cfg: rd.luks.uuid=luks-57af8 vs. rd.luks.uuid=luks-57af8f53-0de0-4e88-975e-d859de918ca8
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.