Description of problem: When showing a traceback of VdsmError, there is no info about the nature of the error, making debugging impossible. Thread-14492::ERROR::2015-01-13 12:21:09,717::__init__::491::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/yajsonrpc/__init__.py", line 486, in _serveRequest res = method(**params) File "/usr/share/vdsm/rpc/Bridge.py", line 285, in _dynamicMethod ret = self._getResult(result, retfield) File "/usr/share/vdsm/rpc/Bridge.py", line 103, in _getResult raise VdsmError(5, "Response is missing '%s' member" % member) VdsmError Version-Release number of selected component (if applicable): vdsm-4.16.7-1.gitdb83943.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Try to extend block domain with bad LUN Actual results: VdsmError Expected results: VdsmError: Response is missing 'membername' member
Should be trivial change (implement __str__ properly or fix the error handler), and will make it possible to debug such failures.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Jiri, I don't have any information about reproducing this, only what you see in the bug description. Basically this is code change that make it easier to debug errors, not a user visible feature, so I don't think we should waste too much time on this bug.
ok, codechange flag - vdsm-4.17.15-0.el7ev no strange behaviour observed.
oVirt 3.6.0 has been released, closing current release