Comment 1 for bug 1593364

Well, did some investigation upon the issue and how it can be fixed (from the description that was provided and understood). It looks like it's related to this particular method which stands for logging activities: https://github.com/openstack/fuel-qa/blob/master/fuelweb_test/__init__.py#L49

Going from that point what can be done:

1. Full traceback printing can be used.
One of the draft attempts can look like this: http://paste.openstack.org/show/538803/
This draft produces the output something like this: http://paste.openstack.org/show/538804/
Not sure it's useful though.

2. 'inspect' module can be utilized to get source code and to extract decorator method name. In this case printing debug stacktrace method in case of exception might be overwritten. In theory it can be done, but the drawbacks I can see are: shadowing native Python stacktrace, what if problem occurs inside decorator; there can be more code that we can initially expect to fix all that stuff. The quick take with 'inspect' module didn't allow to get the decorator method name...

@Maksym, please, provide your vision on that and let me know if I missed the point.