Dafna, Do you think this one should block 883877 ?
I don't understand the bug nor its title, engine is just reflecting what VDSM returned to it, what the expected results?
(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.
Vered, is this still relevant?
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.