Hide Forgot
Description of problem: When we performed some operation using rhui-manager and if something went wrong, we usually got following error message: An unexpected error has occurred during the last operation. More information can be found in /root/.rhui/rhui.log. For example.. ================ ( Please consider the following error messages just as an example; here the objective is to improve the error handling ) I was trying to unregister a CDS using rhui-manager and got the same error on stdout. rhui.log says: ================= ServerRequestError: (500, u"PulpException: u'Communications error while attempting to release CDS [dhcp193-73.pnq.redhat.com]; check the server log for more information' pulp.log says: ================ PulpException: u'Communications error while attempting to release CDS [dhcp193-73.pnq.redhat.com]; check the server log for more information' So from end user perspective, the error message in log should also be on stdout. Version-Release number of selected component (if applicable): pulp 0.171 rhui-tools 2.0.22 How reproducible: everytime Steps to Reproduce: 1. 2. 3. Actual results: An unexpected error has occurred during the last operation. More information can be found in /root/.rhui/rhui.log. Expected results: Error message in logs should be on stdout, like: Communications error while attempting to release CDS [dhcp193-73.pnq.redhat.com]; More information can be found in /root/.rhui/rhui.log. Additional info:
Punting to 2.1 because I'm not sure I'll have the time to go through each place an exception is caught and parse out the error message (hopefully by then Pulp will be more consistent with error messages and this will be cleaner).
added to rhui-20 tracker
I said "punting to 2.1", not sure why this was added to the rhui-20 tracker.
moving to version 2.1.1
Valid in RHUI3.