Bug 1082110

Summary: Event ID 1200 (VM rename) does not record the initating User id
Product: Red Hat Enterprise Virtualization Manager Reporter: Paul Dwyer <pdwyer>
Component: ovirt-engine-webadmin-portalAssignee: Eli Mesika <emesika>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: low Docs Contact:
Priority: low    
Version: 3.2.0CC: aberezin, bazulay, ecohen, gklein, iheim, jbelka, ofrenkel, oourfali, pstehlik, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: All   
OS: All   
Whiteboard: infra
Fixed In Version: ovirt-3.5.0-alpha2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 18:00:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    

Description Paul Dwyer 2014-03-28 17:01:39 UTC 
Description of problem:
When you rename a VM the event generated (event ID 1200) does not contain the username who made the change in the description.

Version-Release number of selected component (if applicable):
RHEVM 3.2.3-0.42

How reproducible:
Always

Steps to Reproduce:
1. edit VM, change name
2. event alert is generated, check description

Actual results:
See attached screenshot


Expected results:
Username should be available in description for auditing purposes

Additional info:
Same happens in RHEV3.3.0, not managed to test later versions so far.
Comment 4 Jiri Belka 2014-08-07 13:55:31 UTC 
ok, ovirt-engine-webadmin-portal-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch

2014-Aug-07, 15:52
VM test configuration was updated by admin.
	
2014-Aug-07, 15:52
VM test was renamed from test to sandokan by admin.
                                          ^^^^^^^^^ ok ;)
Comment 6 errata-xmlrpc 2015-02-11 18:00:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html