Bug 1395793 - Cloning VM will cause both source VM's and cloned VM's disks to stay in locked state
Summary: Cloning VM will cause both source VM's and cloned VM's disks to stay in locke...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.0.6
: 4.0.6.3
Assignee: Tal Nisan
QA Contact: Raz Tamir
URL:
Whiteboard:
: 1404143 1410702 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 16:47 UTC by Raz Tamir
Modified: 2019-04-28 14:16 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-18 07:28:10 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: ovirt-4.1+
rule-engine: blocker+

Attachments (Terms of Use)
engine and vdsm logs (38.37 KB, application/x-gzip)
2016-11-16 16:47 UTC, Raz Tamir 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 67892 0 master MERGED core: Fix CloneVmCommand when the VM is based on template 2016-12-08 09:40:00 UTC
oVirt gerrit 67973 0 ovirt-engine-4.0 MERGED core: Fix CloneVmCommand when the VM is based on template 2016-12-08 10:54:01 UTC
oVirt gerrit 67979 0 ovirt-engine-4.0.6 MERGED core: Fix CloneVmCommand when the VM is based on template 2016-12-08 11:06:03 UTC

Description Raz Tamir 2016-11-16 16:47:01 UTC 
Created attachment 1221292 [details]
engine and vdsm logs

Description of problem:
When cloning a VM, the cloned VM's disk and the source VM's disk stays in locked state.
Checked over NFS and iSCSI storage domains


Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0-0.0.master.20161115231325.gitd073048.el7.centos.noarch
vdsm-4.18.999-886.git65fc84b.el7.centos.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Create a VM
2. Clone the vm - press 'Clone VM'
3.

Actual results:
Both disks, the source and the cloned will remain in locked state

Expected results:


Additional info:
No errors in the engine or vdsm logs
Comment 1 Allon Mureinik 2016-11-17 15:48:00 UTC 
Raz, can you confirm that this *doesn't* happen in 4.0.z?
Comment 2 Raz Tamir 2016-11-21 15:01:54 UTC 
Seems like this is not a regression. Just managed to reproduce this in 4.0.6 as well.
Comment 3 Moran Goldboim 2016-11-30 12:05:15 UTC 
shouldn't it be a 4.0.6 blocker than?
Comment 4 Tal Nisan 2016-11-30 12:06:46 UTC 
Raz, I could not reproduce, can you please try and reproduce on master again?
Comment 5 Raz Tamir 2016-11-30 12:12:37 UTC 
Tal I'm sorry for the unclear steps to Reproduce:
1. Cloned a VM from template as thin copy
2. Clone the vm from step 1 - press 'Clone VM'
Comment 6 Raz Tamir 2016-12-11 15:50:11 UTC 
Verified on 4.0.6.3-0.1.el7ev.

This should be cloned to 4.1 as well right Tal?
Comment 7 Tal Nisan 2016-12-12 10:26:10 UTC 
It's an oVirt bug, no need for clones, should be tested on both 4.0.z and 4.1 though
Comment 8 Tal Nisan 2016-12-13 10:14:13 UTC 
*** Bug 1404143 has been marked as a duplicate of this bug. ***
Comment 9 Tal Nisan 2017-01-09 09:57:34 UTC 
*** Bug 1410702 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.