Re: [ovirt-devel] improving VDSM error reporting
well, we can add the python text, and the UX team will decide under what circumstances to
display it. At least for some users it will add information.
----- Original Message -----
From: "Dan Kenigsberg" <danken(a)redhat.com>
To: "Yoav Kleinberger" <ykleinbe(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Tuesday, May 13, 2014 4:08:47 PM
Subject: Re: [ovirt-devel] improving VDSM error reporting
On Tue, May 13, 2014 at 08:31:16AM -0400, Yoav Kleinberger wrote:
Hi Dan,
A few points:
1. I explained the problem using the existing "message" field. An old VDSM will
have the "meaningless" messages, and when working with a new engine they will be
displayed to the user.
As I have shown, "message" is not completely meaningless as it is
(though it certainly does not add much information beyond the error
code). I don't suspect that Engine would show the extra "details" to
just any user. UX folks like to keep the GUI clean and tidy, so only
experienced users with the right credentials would see them. In some
(most) cases, "message" would add no information beyond the error code
and its localized string. But as time passes, we can add more and more
"meat" to the message.
2. The patch you attached generates the message inside the code for a
specific circumstance. However, I want to handle unexpected errors that fly out of the
code in a generic way, without needing to understand each and every case.
unexpected errors end up with code error 16 and message 'Unexpected
exception'. Personally, I'd love to replace this message with a
meaningful traceback.
Dan.