Hide Forgot
Description of problem: I'm trying to upgrade a fully updated F19 (running on virtualbox if it matters). It fails post reboot - it reboots to the fedup image, but then reboots again - and I'm not sure why (can't find logs for it). I have 347MB free in /boot before the reboot (with the fedup initramfs image already). Possibly unrelated, running 'fedup -d --network 20' (which seems to succeed) I get the following exception in the log: [ 29.386] (DD) fedup.yum:treeinfo() fetching .treeinfo from repo 'default-installrepo' [ 31.229] (II) fedup:<module>() Exception: Traceback (most recent call last): File "/bin/fedup", line 181, in <module> main(args) File "/bin/fedup", line 120, in main kernel, initrd = f.download_boot_images() # TODO: force arch? File "/usr/lib/python2.7/site-packages/fedup/download.py", line 293, in download_boot_images conf.set("boot", "kernel", kernel) UnboundLocalError: local variable 'kernel' referenced before assignment Since the virtualbox crashed once when I tried, I caught the following error: dracut-pre-pivot[480]: Warning UPGRADEROOT ius unset, can't save initramfs but then it continued... Version-Release number of selected component (if applicable): fedup-0.7.3-4.fc19.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please update fedup to 0.8.0-3 and try again. Thanks.
(In reply to Chris Murphy from comment #1) > Please update fedup to 0.8.0-3 and try again. Thanks. Looks much better. Did not see the exception and the post-reboot behavior seems positive - it began updating the packages.
Similar problem. Conditions: Fully up to date F19 installation, including fedup-0.8.0-3.fc19.noarch, using: fedup --reboot --network 20 Results: (1) Downloads lots of RPMs successfully, then reboots to System Upgrade (later, fedup.log shows "installing" for all .rpm files, creating module new boot entry, and clean exit) (2) System Upgrade runs successfully (it takes a while), then reboots again; but System Upgrade boot entry is still default, and there are no F20 boot entries (3) Upon reboot to System Upgrade again, still running F19, but with F20 kernel, and network/rpcbind/iptables/ip6tables problems, no F20 kernel in /boot, and no F20 packages in rpm database Why? Is there a workaround?
This problem is still present three months later. Fedup is broken, because it doesn't upgrade any packages, doesn't put a kernel in /boot, etc. I finally upgraded F19->F20 using the yum-upgrade method. Too bad -- fedup method would be nicer if it worked, but it doesn't.
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.