Bug 922554 - Both frontend logs and engine log show the vdsm error key in lowercase for some Storage flows, instead of original VDSM key and actual description.
Summary: Both frontend logs and engine log show the vdsm error key in lowercase for so...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.4.0
Assignee: Vered Volansky
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-17 20:43 UTC by Vered Volansky
Modified: 2016-02-10 20:24 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 883877
Environment:
Last Closed: 2013-12-19 08:29:18 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 10966 0 None None None Never

Comment 1 Vered Volansky 2013-03-17 20:47:13 UTC
Dafna, Do you think this one should block 883877 ?

Comment 2 Haim 2013-03-17 20:59:07 UTC
I don't understand the bug nor its title, engine is just reflecting what VDSM returned to it, what the expected results?

Comment 3 Vered Volansky 2013-03-17 21:15:51 UTC
(In reply to comment #2)
> I don't understand the bug nor its title, engine is just reflecting what
> VDSM returned to it, what the expected results?

Revised title.

Actual Results:
1. Engine log shows the Vdsm key/ VDSMErrors key after lower-casing the capitals in the key (no CamelCase). 

2. Audit log shows the Vdsm key/ VDSMErrors key after lower-casing the capitals in the key (no CamelCase).

Expected Results:
1. Engine log should show the original VDSMErrors key, without lower casing it (CamelCase).

2. Audit log should show the description of the above key, not the key itself, or the camelcase of it.

Comment 4 Ayal Baron 2013-12-18 09:48:12 UTC
Vered, is this still relevant?

Comment 5 Vered Volansky 2013-12-19 08:29:18 UTC
Now the vdsm exception is no longer lowered-cased, and the correct error message appears in the engine log. No message in the audit log, though a popup witht he correct message did pop up, so presumably that was intentional.
Closing u/s.


Note You need to log in before you can comment on or make changes to this bug.