Bug 1004112
Summary: | continuous abrt spam: ImportError: No module named transaction | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rik van Riel <riel> |
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | james.antill, mzazrivec |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-04 09:50:25 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
Rik van Riel
2013-09-04 01:28:39 UTC
As an aside, the file /usr/lib/python2.6/site-packages/rpmUtils/transaction.py, which the error message suggests does not exist, actually does exist, permissions look ok, and "rpm -V yum" reports no mismatches. Yes, this happens b/c some crash happens on your system, abrt catches it and while creating the crash report, abrt tries to run sosreport, which crashes b/c of a module import error -> here we are. This will be resolved in RHEL-6.5 with bug #983999. *** This bug has been marked as a duplicate of bug 983999 *** |