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

Bug 1568556

Summary:	LiveMerge releases VM lock twice
Product:	[oVirt] ovirt-engine	Reporter:	Ravi Nori <rnori>
Component:	BLL.Virt	Assignee:	Ravi Nori <rnori>
Status:	CLOSED DUPLICATE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lsvaty, mperina
Target Milestone:	ovirt-4.3.0	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-01 19:03:14 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 Ravi Nori 2018-04-17 18:37:20 UTC

Description of problem: Deleting a snapshot while the VM is running results in the VM lock being released twice.


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


How reproducible:


Steps to Reproduce:
1. Create a VM snapshot
2. Run the VM
3. Delete the snapshot

Actual results:
Warning message in logs about lock being released which has already been released

2018-04-17 14:32:50,233-04 WARN  [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [346c1aeb-bbf5-4ba8-b661-c58f940c3b59] Trying to release exclusive lock which does not exist, lock key: 'd69cf8da-f93b-48e7-a178-deb991a45909VM'

Expected results:
No warning message

Comment 1 Martin Perina 2018-04-18 06:53:08 UTC

Setting priority to high, because other flow can step in and perform action during the time between child command releases the lock and parent command finishes its execution and try to release the lock again (locks acquired in parent command cannot be released in child commands).

Comment 2 Ravi Nori 2018-08-01 19:03:14 UTC


*** This bug has been marked as a duplicate of bug 1581158 ***