Bug 966192

Summary:	PRD33 - AuditLogDirector.log(*) methods should also update engine.log
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Keith Robertson <kroberts>
Component:	RFEs	Assignee:	Spenser Shumaker <sshumake>
Status:	CLOSED ERRATA	QA Contact:	movciari
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, bazulay, iheim, jmoran, kroberts, lpeer, pstehlik, sshumake, talayan, thildred, yeylon, yzaslavs
Target Milestone:	---	Keywords:	Improvement
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	is6	Doc Type:	Enhancement
Doc Text:	AuditLogDirector.log(*) methods now update engine.log, so every event that appears in the administration portal's event viewer is logged permanently to the log file.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 17:22:03 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:

Description Keith Robertson 2013-05-22 18:18:25 UTC

1. Proposed title of this feature request
AuditLogDirector.log(*) methods should also update engine.log

2. Who is the customer behind the request?
Red Hat 

3. What is the nature and description of the request?
Currently, events that appear in the admin console's event viewer do not appear in the engine log file (ie. engine.log).  This is bad form.  Every event that appears in the admin console's event viewer should be logged permanently to the log file for posterity.  There should never be a case where an event appears in the event viewer and is not simultaneously sent to the log file.

4. Why does the customer need this? (List the business requirements here)
Diagnostic services.

5. How would the customer like to achieve this? (List the functional requirements here)
1) Log all events that appear in the event viewer to the log file.
2) All of the event attributes should be sent to the log file not just a subset.  This means that every column from the audit_log SQL table which is the backing table for the event viewer should be sent to the log file.

6. List any affected packages or components.
The Red Hat Support Plug-in for RHEV is adversely affected by the fact that this information is not logged.

7. Would the customer be able to assist in testing this functionality if implemented?
Yes.

Comment 3 yeylon@redhat.com 2013-06-26 18:18:22 UTC

what we need to test here?

Comment 4 Spenser Shumaker 2013-06-26 19:06:06 UTC

Hi Yaniv,

We will need to test that all events logged in the event viewer are now logged in the log file.  The test I used for this was logging in and out of the product, which should appear in engine.log.

Comment 5 Charlie 2013-11-28 00:16:54 UTC

This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 6 errata-xmlrpc 2014-01-21 17:22:03 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.

http://rhn.redhat.com/errata/RHSA-2014-0038.html