Red Hat Bugzilla – Bug 614139
Report throws traceback when there is a configuration for a non-present plugin
Last modified: 2010-11-10 16:29:48 EST
Description of problem:
During testing, I modified my main configuration file at /etc/report.conf to include config for all plugins. After uninstalling plugin for bugzilla (obsoleted now), I am getting traceback because of bugzilla plugin config is still present in main config:
[dkutalek@timothy Documents]$ report /tmp/dummy-report.txt
Traceback (most recent call last):
File "/usr/bin/report", line 160, in <module>
app = report.report(signature, io, **optsDict)
File "/usr/lib64/python2.6/site-packages/report/__init__.py", line 489, in report
choice = buildChoices(signature, io, config, rptopts)
File "/usr/lib64/python2.6/site-packages/report/__init__.py", line 398, in buildChoices
(modulefile, modulepath, moduletype) = imputil.imp.find_module(moduleName,alternatives.__path__)
ImportError: No module named RHEL-bugzilla
Although it can be considered as misconfiguration by user, it definitely should not traceback because of it. Giving a simple text warning to stderr and continue should be nice enough.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. insert a configuration for any uninstalled plugin
2. run report
Only give a warning and continue.
Under usual circumstances not triggered, because configuration for individual plugins is kept in separate files and these are removed when removing plugin via package dependency. However, it can happen when user plays with main config as happened to me.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.