Description of problem: sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64 ... Traceback (most recent call last): File "/bin/fedup-cli", line 285, in <module> main(args) File "/bin/fedup-cli", line 257, in main prep_boot(kernel, initrd) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 373, in prep_boot modify_bootloader(kernel, initrd) File "/usr/lib/python2.7/site-packages/fedup/download.py", line 356, in modify_bootloader for e in bootloader.get_entries(): File "/usr/lib/python2.7/site-packages/fedup/grubby.py", line 69, in get_entries ents.append(self.get_entry(n)) File "/usr/lib/python2.7/site-packages/fedup/grubby.py", line 63, in get_entry return GrubbyEntry(**info) TypeError: __new__() takes exactly 7 arguments (6 given) Version-Release number of selected component (if applicable): Fedora 17, fully updated fedup-0.7.1-1.fc17 How reproducible: sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64 Steps to Reproduce: 1. update Fedora 17 2. install fedup (yum --enablerepo=updates-testing install fedup) 3. Run fedup-cli: sudo fedup-cli --network 18 --debuglog fedupdebug.log --instrepo=http://tflink.fedorapeople.org/fedup/f18-upgrade/x86_64 Actual results: TypeError: __new__() takes exactly 7 arguments (6 given) Expected results: Upgraded system Additional info: Since I saw the grubby error I figured it might have to do with the fact that I am not using the initrd part (root=/dev/sda1 rootfstype=ext4). If I revert that change fedup-cli returns no errors.
Exactly the same error for me. In my context, I have fedup once with no problem then when I rebooted and ran the system upgrage in GRUB2, the system remained stuck for half an hour after the bars at the bottom of the screen "completed". I had to restart my PC. Then Fedora 18 crashed at boot (unable to mount FS). I tried to restart the system upgrade in grub with no effect. So I restarted on my "old" F17 and tried to re run fedup and now I have this error. When I look at my grub config, the only difference betweenF17 and F18 is that there is no initrd line in F18.
Yup, good catch - the traceback here is because fedup's grubby module assumes that any boot entry will have all six items (index, root, args, kernel, initrd, title).. and sometimes that isn't true. The fix for this is pretty simple. Should be in git shortly.
*** Bug 882437 has been marked as a duplicate of this bug. ***
*** Bug 883258 has been marked as a duplicate of this bug. ***
*** Bug 883659 has been marked as a duplicate of this bug. ***
*** Bug 883660 has been marked as a duplicate of this bug. ***
fedup-0.7.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedup-0.7.2-1.fc17
Package fedup-0.7.2-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.2-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20801/fedup-0.7.2-1.fc17 then log in and leave karma (feedback).
fedup-0.7.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.