Bug 1404143 - Disks are locked after VM clone
Summary: Disks are locked after VM clone
Keywords:
Status: CLOSED DUPLICATE of bug 1395793
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.0.6
: ---
Assignee: Tal Nisan
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 07:49 UTC by rhev-integ
Modified: 2016-12-13 10:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-13 10:14:13 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rhev-integ 2016-12-13 07:49:03 UTC
Description of problem:
I have tried to clone a VM. Clone completed successfully according to the logs but both disks are still locked (of the VM I have cloned from and the new VM).

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


How reproducible:
Disks are still locked currently in our (rhv-devops team) integration engine.
address: integration-engine.eng.lab.tlv.redhat.com
UI - 
user: <kerberos user>
pass: <kerberos password>

SSH -
user: root
pass: <usual root password>

Steps to Reproduce:
1. Power off VM
2. right click menu and clone VM
3. Enter new VM's name and press ok

Actual results:
Clone completes successfully but I can't start both VMs because both disks are locked

Expected results:
Clone completes successfully and I can start both VMs

Additional info:

Comment 1 Tal Nisan 2016-12-13 10:14:13 UTC
Next time please open bugs with your own user so I'll know who to contact when needed, also please attach logs and supply exact Engine/VDSM version.

Anyway, logged into the machine and it seems it's running:
ovirt-engine-4.0.5.5-0.1.el7ev.noarch
So this is a dup of bug 1395793 which was fixed in 4.0.6.3

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


Note You need to log in before you can comment on or make changes to this bug.