Bug 902555
| Summary: | fedup left my system unbootable due to systemd.unit=system-upgrade.target | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andy Lutomirski <luto> |
| Component: | fedup | Assignee: | Will Woods <wwoods> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | dshea, luto, tflink, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-01 13:19: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: | |
| Embargoed: | |||
Andy, did you install any kernel updates between running fedup and rebooting into the upgrade? Can you post your grub.conf file? I've tested upgrading a system using grub-0.97 from F17 to F18, and the systemd.unit argument is only added to the new entry created for fedup in grub.conf. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. For the record, this should be fixed by fedup-0.8.0, which no longer requires the extra boot arguments. fedup-0.8.0 indeed worked fine for me when upgrading two machines to F20. Hooray! Let's change this to a slightly more positive outcome, then. *** This bug has been marked as a duplicate of bug 964303 *** |
I upgraded from a freshly updated F17 to F18 a couple of hours ago. The upgrade worked fine, but the subsequent reboot got stuck forever. The apparent cause is this crap in my grub.cfg: title Fedora (3.7.2-204.fc18.x86_64) root (hd0,2) kernel /vmlinuz-3.7.2-204.fc18.x86_64 rd.md=0 rd.dm=0 rd.lvm.lv=vg_amaluto/root KEYTABLE=us rd.luks.uuid=luks-cd5b520b-745e-4a9b-bebf-d9f094487d20 SYSFONT=True ro root=/dev/mapper/vg_amaluto-root rd.lvm.lv=vg_amaluto/swap LANG=en_US.UTF-8 rhgb quiet upgrade systemd.unit=system-upgrade.target plymouth.splash=fedup initrd /initramfs-3.7.2-204.fc18.x86_64.img Removing systemd.unit=system-upgrade.target fixed the problem and my system booted into F18 successfully. (Note: this is grub, not grub2. This might be part of the cause.)