Description of problem: Create snanpshot releases Vm lock twice
Version-Release number of selected component (if applicable): 4.3
Steps to Reproduce:
1. Create a VM snapshot from Webadmin
A warning message in logs indicating that the VM lock is being released twice
2018-04-19 11:29:05,405-04 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engine-Thread-323) [50b50be7-e35e-415d-8c82-3cddce48a87b] Trying to release exclusive lock which does not exist, lock key: 'd69cf8da-f93b-48e7-a178-deb991a45909VM'
No warning message about lock being released twice
(In reply to Yaniv Kaul from comment #1)
Forwarding to Michal, infra don't know the flow that well to asses the severity properly. We just know that lock was released prematurely in child command and within time when child command released the lock and parent command finishes other flow can obtain the lock and perform actions dangerous to original command
no idea. If OST is green then probably medium severity at most
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Closing old bug. Please reopen if still relevant/you want to work on it.