Bug 1293663

Summary: Disk remains locked after create snapshot
Product: [oVirt] ovirt-engine Reporter: Arik <ahadas>
Component: BLL.StorageAssignee: Liron Aravot <laravot>
Status: CLOSED CURRENTRELEASE QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.0.0CC: ahadas, amureini, bugs, derez, gklein, laravot, stirabos, tnisan, ylavi
Target Milestone: ovirt-3.6.2Keywords: Regression
Target Release: 3.6.2.5Flags: rule-engine: ovirt-3.6.z+
rule-engine: blocker+
ylavi: planning_ack+
tnisan: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:12:25 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
engine log
none
vdsm logs (tar file) none

Description Arik 2015-12-22 15:45:34 UTC 
Description of problem:
When taking a snapshot for VM with one disk, the disk remains lock.

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


How reproducible:
Not always

Steps to Reproduce:
1. Run a VM
2. Take (live) snapshot (with memory - I don't think it matters)
3.

Actual results:
The snapshot is created successfully but the disk remains lock long after the operation is finished.

Expected results:
The lock for the disk should be released.

Additional info:
I also get 2 audit logs that say "snapshot ... creation for .. has been completed"
it seems that for some reason the command is ended successfully twice..
Comment 1 Arik 2015-12-22 15:46:12 UTC 
Created attachment 1108663 [details]
engine log
Comment 2 Arik 2015-12-22 15:47:02 UTC 
Created attachment 1108665 [details]
vdsm logs (tar file)
Comment 3 Gil Klein 2015-12-22 17:29:31 UTC 
*** Bug 1293662 has been marked as a duplicate of this bug. ***
Comment 4 Arik 2015-12-23 08:50:55 UTC 
VDSM: 
Version     : 4.17.999
Release     : 358.git9017028.fc22

Engine:
last commit: 7a18121ca5fe1eb45ddbf9e76af403614352a366
Comment 5 Allon Mureinik 2015-12-23 09:19:26 UTC 
Daniel, haven't we seen this already?
Comment 6 Daniel Erez 2015-12-23 09:33:23 UTC 
(In reply to Allon Mureinik from comment #5)
> Daniel, haven't we seen this already?

Had a few similar issues but not sure it's related.
@Arik - is it happening constantly on latest master?
Comment 7 Tal Nisan 2015-12-23 09:37:00 UTC 
Seems like Liron already solved the issue, updated the tracker
Comment 8 Arik 2015-12-23 09:41:31 UTC 
(In reply to Daniel Erez from comment #6)
> (In reply to Allon Mureinik from comment #5)
> > Daniel, haven't we seen this already?
> 
> Had a few similar issues but not sure it's related.
> @Arik - is it happening constantly on latest master?

No, not always.
Same as we saw in your env.
Comment 9 Kevin Alon Goldblatt 2016-02-03 19:45:12 UTC 
Verified with the following code:
----------------------------------
rhevm-3.6.3-0.1.el6.noarch
vdsm-4.17.19-0.el7ev.noarch

Verified with the following scenario:
--------------------------------------
Steps to Reproduce:
1. Run a VM
2. Take (live) snapshot (with memory - I don't think it matters) >>>>> The snapshot is created successfully and the lock for the disk is released.

Moving to VERIFIED!