Bug 1043981
| Summary: | [abrt] fedup: fedup-cli:216:main:AttributeError: 'ProblemSummary' object has no attribute 'format_details' | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vladimir Krcho <vlkovo> | ||||||||
| Component: | fedup | Assignee: | Will Woods <wwoods> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 20 | CC: | bugreporter1, djuran, jeff, jon.dufresne, m.a.young, sgrubb, tflink, wwoods | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/042a217726e325282714edf28971d4d168a1218c | ||||||||||
| Whiteboard: | abrt_hash:a05d11ca13f327068dcee22d0850683b0b06a542 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-06-30 01:33:52 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Vladimir Krcho
2013-12-17 14:43:21 UTC
Created attachment 837708 [details]
File: backtrace
Created attachment 837709 [details]
File: environ
I believe the *traceback* would be fixed by this commit: https://github.com/wgwoods/fedup/commit/01e0419 But the traceback happened while fedup was trying to report an error. The original error seems to be a problem with the RPM transaction, which might resolve itself once the affected package(s) are updated. (In reply to Will Woods from comment #3) > I believe the *traceback* would be fixed by this commit: > > https://github.com/wgwoods/fedup/commit/01e0419 > > But the traceback happened while fedup was trying to report an error. > > The original error seems to be a problem with the RPM transaction, which > might resolve itself once the affected package(s) are updated. I applied that patch manually to the upgrade.py file and fedup (from F19 to F20 using --iso) now starts upgrading following the reboot (the conflict in my case turned out to be avahi.x86_64 with avahi-libs.i686 which I should be able to fix afterwards). So, is this fix going to be pushed out to F19? I also have an upgrade that crashes setting up the upgrade. I have no idea if its safe to reboot into the upgrade or how to rollback anything that was prepared. IOW, it would be great if a fix was pushed out. It's being worked on. Got 56 other new bug reports to sort through first. Can you attach your fedup.log so I can try to figure out the actual cause of the RPM transaction problem? Created attachment 853003 [details]
Here is fedup.log
After unsuccesfull upgrade by fedup i upgraded to f20 by yum.
I don't have the logs. I had a small window of time to upgrade the system and decided to go with yum distro-sync. I have another couple of systems to upgrade and if I run into a problem, I will get the logs. But if you have a large number of bugs, maybe a couple updates is in order? Thanks. I have a large number of bug *reports*. The actual number of bugs is small, but bug triage takes time. If you want to get fixes faster, help with bug triage. *** Bug 1044517 has been marked as a duplicate of this bug. *** *** Bug 1079370 has been marked as a duplicate of this bug. *** *** Bug 1079369 has been marked as a duplicate of this bug. *** fedup-0.8.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc19 fedup-0.8.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc20 Package fedup-0.8.1-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-0.8.1-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7085/fedup-0.8.1-1.fc19 then log in and leave karma (feedback). fedup-0.8.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. I am trying to upgrade from Fedora Core 18 -> FC20 via the following fedup command: sudo fedup --network 20 and am getting the same error as described in this bug report. If I understood correctly, it is fixed in FC19 and FC20. Will the fix be back-ported to FC18? Thanks and regards, Jeff Klein fedup-0.9.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.9.0-1.fc19 fedup-0.9.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/fedup-0.9.0-2.fc19 fedup-0.9.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. 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. |