No fc18 boot image was created after upgrade and grub2 was not updated I was upgrading from fc17 I issued the following command sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/fedora/linux/releases/test/18-Beta/Fedora/x86_64/os/ The install and packages were downloaded with no error messages, I rebooted and selected "Upgrade System", I was asked for the encryption password on the hard drive which I entered, when the progress bar screen came up I pressed escape and was left with an almost blank screen with a couple of lines. I came back to the machine after some time and it had rebooted and was at the login screen. After logging in uname -a still reported fc17, I rebooted and there was no option for fc17 in grub, I checked /boot and no fc18 image was created. rpm -qa | grep fc18 indicates 1682 fc18 packages were installed although not kernel rpm -qa | grep fc17 returns 88 packages remaining, including kernel. I have no fedup log as I since tried to rerun it and overwrote the initial log. fedup now blows up with the following error BDB2053 Freeing read locks for locker 0x63: 3708/140613751445440 Traceback (most recent call last): File "/bin/fedup-cli", line 330, in <module> main(args) File "/bin/fedup-cli", line 275, in main pkgs = download_packages(f) File "/bin/fedup-cli", line 61, in download_packages f.download_packages(updates, callback=output.DownloadCallback()) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 210, in download_packages if set(updates) != set(pkgs): TypeError: 'NoneType' object is not iterable
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
*** This bug has been marked as a duplicate of bug 904112 ***