Created attachment 679784 [details] FedUp Debug Log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create new Fedora 17 64-bit install on Linode 2. Update to latest version of all packages 3. reboot 4. run fedup-cli --network 18 --debuglog fedupdebug.log Actual results: esting upgrade transaction rpm transaction 100% [=========================================================================] rpm install 100% [=============================================================================] setting up system for upgrade Traceback (most recent call last): File "/usr/bin/fedup-cli", line 330, in <module> main(args) File "/usr/bin/fedup-cli", line 291, in main prep_boot(kernel, initrd) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 401, in prep_boot modify_bootloader(kernel, initrd) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 397, in modify_bootloader boot.add_entry(kernel, initrd, banner=_("System Upgrade"), kargs=args) File "/usr/lib/python2.7/site-packages/fedup/boot.py", line 39, in add_entry return check_output(cmd, stderr=PIPE) File "/usr/lib64/python2.7/subprocess.py", line 537, in check_output process = Popen(stdout=PIPE, *popenargs, **kwargs) File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__ errread, errwrite) File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory Expected results: Additional info:
please change the title from 'Traceback' to something maybe more like "fedup Exception Traceback File /usr/bin/fedup-cli line 330 in <module> main(args)"
Created attachment 684523 [details] debug log for fedup error: File "/usr/bin/fedup-cli", line 330, in <module> main(args) besides the error there are seberal lines like: 203.120] (DD) fedup.depsolve:procReqPo() req po: perl(Test::Refcount) → perl-IO-Async-0.29-9.fc18.noarch and like [ 3631.390] (II) fedup.yum:callback() [Errno 14] HTTP Error 404 - Not Found : http://mirror.us.as6453.net/fedora/linux/updates/testing/18/x86_64/qemu-kvm-1.2.2-3.fc18.x86_64.rpm
Your system seems to be missing the "new-kernel-pkg" command. Is the "grubby" package installed? Is the "new-kernel-pkg" command available?
fedup-0.7.3-0.git20130128.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-0.git20130128.fc17
fedup-0.7.3-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-1.fc17
Package fedup-0.7.3-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.7.3-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3956/fedup-0.7.3-1.fc17 then log in and leave karma (feedback).
fedup-0.7.3-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc18
fedup-0.7.3-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc17
fedup-0.7.3-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc17
fedup-0.7.3-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc18
fedup-0.7.3-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc19
fedup-0.7.3-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.7.3-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.3-5.fc17
fedup-0.7.3-4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
fedup-0.7.3-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.