Bug 1381562 - [z-stream clone - 4.0.5] "Started - Finished" Messages in the audit log without any information
Summary: [z-stream clone - 4.0.5] "Started - Finished" Messages in the audit log witho...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.7
Hardware: All
OS: Linux
high
medium
Target Milestone: ovirt-4.0.5
: 4.0.5
Assignee: Eli Mesika
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On: 1372320
Blocks: 1396586
TreeView+ depends on / blocked
 
Reported: 2016-10-04 12:46 UTC by rhev-integ
Modified: 2020-04-15 14:42 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Updated messages written to the audit log. Previously backup execution start and finish events were identified only with "Started"/"Finished" values, so it was not obvious which process has started or finished. Events now have the format "Backup started at ..." and "Backup finished at ...".
Clone Of: 1372320
: 1396586 (view as bug list)
Environment:
Last Closed: 2016-11-16 15:31:15 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2786 0 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0.5 2016-11-16 20:24:41 UTC
oVirt gerrit 63989 0 master MERGED core: fix backup log messages 2016-10-04 12:46:36 UTC
oVirt gerrit 64189 0 ovirt-engine-4.0 MERGED core: fix backup log messages 2016-10-04 12:46:36 UTC

Comment 1 Nisim Simsolo 2016-10-09 13:12:14 UTC 
Verified:
rhevm-4.0.5-0.1.el7ev.noarch

Verification scenario:
1. run engine-backup command. 
2. Verify Backup Started and Backup Finished events are listed in events tab.
Comment 3 errata-xmlrpc 2016-11-16 15:31:15 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/RHBA-2016-2786.html
Note You need to log in before you can comment on or make changes to this bug.