+++ This bug was initially created as a clone of Bug #1003709 +++

Description of problem:
The exception details are not logged if an XML-RPC call throws an exception in one of the Beaker lab controller daemons.

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

Steps to Reproduce (for example):
1. Break beaker-proxy's ability to run 'sudo beaker-clear-netboot', for example by commenting out the lines in /etc/sudoers.d/beaker_proxy_clear_netboot
2. Make a call to beaker-proxy to clear netboot for some system, using XML-RPC:

>>> import xmlrpclib
>>> s = xmlrpclib.ServerProxy('http://localhost:8000/RPC2')
>>> s.clear_netboot('testsystem.example.com')

Actual results:
Clients receive an XML-RPC fault, which is correct, but on the beaker-proxy side nothing useful is logged indicating that the request failed, or why.

Expected results:
Log messages in /var/log/beaker/proxy.log showing that the request failed, and why (including, for the particular example, the error message from sudo or beaker-clear-netboot if there was one).

Additional info:
This was originally reported as part of bug 1003709, but the resolution there only addressed the HTTP side of the problem. This bug now covers the XML-RPC side.