Bug 881338
| Summary: | TypeError: __new__() takes exactly 7 arguments (6 given) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Freddy Willemsen <freddy> |
| Component: | fedup | Assignee: | Will Woods <wwoods> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | npatil, olivier.levillain, pablomg+fedora, thomas.mey, wwoods |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-03 07:26: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: | |||
|
Description
Freddy Willemsen
2012-11-28 18:22:09 UTC
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. |