Bug 922554

Summary:	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.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Vered Volansky <vered>
Component:	ovirt-engine	Assignee:	Vered Volansky <vered>
Status:	CLOSED UPSTREAM	QA Contact:	Aharon Canan <acanan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	abaron, acathrow, amureini, bazulay, cpelland, dron, ewarszaw, hateya, iheim, jkt, lpeer, mkenneth, Rhev-m-bugs, scohen, vered, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	883877	Environment:
Last Closed:	2013-12-19 08:29:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.