Bug 520616

Summary: sectool --info NotAtest --use-dbus throws traceback
Product: [Fedora] Fedora Reporter: Miroslav Vadkerti <mvadkert>
Component: sectoolAssignee: Peter Vrabec <pvrabec>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 11CC: dkopecek, jhrozek, mbarabas, pvrabec
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-01 13:55:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Miroslav Vadkerti 2009-09-01 13:14:30 UTC
Description of problem:

$ sectool --info NotATest --use-dbus
Traceback (most recent call last):
  File "/usr/sbin/sectool", line 438, in run
    else: raise e
DBusException: org.freedesktop.DBus.Python.tuierrors.SecToolActionError: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.6/site-packages/slip/dbus/service.py", line 81, in wrapped_method
    retval = method (self, *p, **k)
  File "/usr/libexec/sectool-mechanism.py", line 108, in infotests
    return self.ST_Action( actions.ST_InfoTests, args, file )
  File "/usr/libexec/sectool-mechanism.py", line 84, in ST_Action
    return self.__perform_action( action, options, file )
  File "/usr/libexec/sectool-mechanism.py", line 74, in __perform_action
  File "/usr/share/sectool/actions.py", line 107, in doAction
  File "/usr/share/sectool/actions.py", line 488, in doStuff
    self.assert_suite_not_empty( suite )
  File "/usr/share/sectool/actions.py", line 120, in assert_suite_not_empty
    raise tuierrors.SecToolActionError(self.name, _("No matching tests to run"))
SecToolActionError: Error: No matching tests to run

Waiting few seconds for thread timeout..

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. sectool --info NotATest --use-dbus
Actual results:

Expected results:
no traceback

Additional info:
With permissive selinux the result is the same.

Comment 1 Maros Barabas 2009-09-01 13:55:11 UTC
When exception occures in backend side of app. dbus will return exception as well, but except tuierrors.SecToolActionError, dbus will raise DBusException: org.freedesktop.DBus.Python.tuierrors.SecToolActionError. 
Traceback is not a bug, unknown messages are written to stderr with traceback. It could be done by catching all possible exceptions we know about, but it's much more (almost useless) code. If somebody want a fix for this issue, please reopen this bug (fix for all exceptions not only this one).