Bug 882644

Summary: [Storage] [Clone VM from snapshot] Destination VM's disk will be inactive if one of the source's disks is shared disk and it's inactive.
Product: Red Hat Enterprise Virtualization Manager Reporter: Leonid Natapov <lnatapov>
Component: ovirt-engineAssignee: Liron Aravot <laravot>
Status: CLOSED CURRENTRELEASE QA Contact: Leonid Natapov <lnatapov>
Severity: unspecified Docs Contact:
Priority: high    
Version: unspecifiedCC: abaron, amureini, dyasny, hateya, iheim, lpeer, Rhev-m-bugs, scohen, sgrinber, yeylon, ykaul
Target Milestone: ---Flags: scohen: Triaged+
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: sf13.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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

Description Leonid Natapov 2012-12-02 13:17:30 UTC
Created attachment 655990 [details]
engine log

[Storage] [Clone VM from snapshot] Destination VM's disk will be inactive if one of the source's disks is shared disk and it's inactive.

How to reproduce:

1.VM with several disk. For example 3 disks.
2.One of the disks is shared disk and it's inactive.
3.Create snapshot.
4.Clone VM from created snapshot.

You will get VM with 2 disks (shared disk not included in the snapshot) but one of the disks (regular disks) will be INACTIVE which will cause to VM's OS to crash on boot.

Reproduced 100% on two different environments after upgrade.
Doesn't happen on clean installation. 

engine log attached.

Comment 1 Alissa 2013-02-05 10:26:40 UTC
There are several things that are not clear in the bug:

1. What are the source and target versions of the upgrade? (from which version is upgrade done and to which version)
2. Is the scenario described here done  after upgrade or before upgrade? or maybe part of it before upgrade and part of it after?
3. Around which hour are the relevant parts in the attached engine.log? It contains info for a big time range...

Comment 2 Leonid Natapov 2013-02-06 13:01:51 UTC
1.from 3.0 (the last build that was released) to 3.1 si24.4
2.After upgrade
3.Don't remember the hours. You can search for cloneVmFromSnapshot, I guess.

Comment 3 Liron Aravot 2013-02-26 14:45:23 UTC
http://gerrit.ovirt.org/#/c/12452/

note the the problem is wider than described - when adding vm from snapshot, the vmdevice information used from the active vm and not from the vm configuration from when the snapshot was taken

Comment 4 Leonid Natapov 2013-04-14 12:05:01 UTC
sf13.1 fixed.

Comment 5 Itamar Heim 2013-06-11 09:25:19 UTC
3.2 has been released

Comment 6 Itamar Heim 2013-06-11 09:30:12 UTC
3.2 has been released

Comment 7 Itamar Heim 2013-06-11 09:45:35 UTC
3.2 has been released