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

Bug 916270

Summary: engine: System throws a "Try to add duplicate audit log values with the same name" error when live migrating the same disk twice
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: abaron, acathrow, derez, dron, iheim, jkt, lpeer, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-18 06:07:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log none

Description Dafna Ron 2013-02-27 17:02:03 UTC
Created attachment 703549 [details]
log

Description of problem:

live storage migration of same vm will cause the following error in engine log:

2013-02-27 06:32:24,395 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-3-thread-42) Try to add duplicate audit log values with the same name. Type: USER_CREATE_SNAPSHOT_FINISHED_SUCCESS. Value: snapsh
otname

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

sf8

How reproducible:

100%

Steps to Reproduce:
1. live storage migrate the same vm's disk
2.
3.
  
Actual results:

we get the following error in engine log" 

2013-02-27 06:32:24,395 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-3-thread-42) Try to add duplicate audit log values with the same name. Type: USER_CREATE_SNAPSHOT_FINISHED_SUCCESS. Value: snapsh
otname

Expected results:

we should not get add duplicate audit log values
if we do, we should not report it as ERROR

Additional info: log

Comment 1 Ayal Baron 2013-07-07 07:55:37 UTC
Dafna, are you trying to migrate the disk while it is already being migrated or after migration finished successfully or after first migration failed?

Daniel, I seem to recall that we already dealt with this error?

Comment 2 Dafna Ron 2013-07-07 13:15:46 UTC
(In reply to Ayal Baron from comment #1)
> Dafna, are you trying to migrate the disk while it is already being migrated
> or after migration finished successfully or after first migration failed?
> 

try to migrate after the first migration finished. 
But I am not sure its relevant any more since the build it was tested on was an early 3.2 build and lots has changed since than. 

> Daniel, I seem to recall that we already dealt with this error?