Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1049292

Summary: [Admin Portal] Events message format handle user causing an event inconsistently
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, iheim, lpeer, oourfali, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-09 06:58:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Jiri Belka 2014-01-07 11:07:18 UTC
Created attachment 846601 [details]
screenshot

Description of problem:
Events message handle user causing an event inconsistently.

Example:

Time | Message
2014-Jan-07, 11:20 | VM admin was created by admin@internal.

2014-Jan-07, 11:20 | Network Interface nic1 (VirtIO) was plugged to VM admin. (User: admin@internal)

Why is it once 'by $user@$domain' and then '(User: $user@$domain)?

Let's make life easier for tools parsing logs (logstash, swatch, whatever-other-tool...)

Version-Release number of selected component (if applicable):
is30 rhevm-3.3.0-0.43.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. create VM, add network card, add disk
2. see event messages for 'VM $vmname was created...' and 'Network Interface $nic ($nic_type) was plugged...'
3.

Actual results:
inconsistency how user is handled in events' message format

Expected results:
keep one format (to make life easier for tools parsing logs)

Additional info:

Comment 1 Jiri Belka 2014-01-07 11:09:54 UTC
I think there should be generally two types of events - internal ones about some internal process - and "external" ones, those which would be interesting for auditing and processing by various parsers. And the latter ones should have similar format if possible.

Comment 2 Oved Ourfali 2014-01-09 06:58:43 UTC
The flows you mentioned all relate to different domains in the system, so please open a separate bug on each such flow, so that we'll be able to assign it to the right people and fix the different issues.