Bug 1105846

Summary: Block Live Storage Migration in case qemu-kvm doesn't support live snapshoting
Product: [Retired] oVirt Reporter: Allon Mureinik <amureini>
Component: ovirt-engine-coreAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Aharon Canan <acanan>
Severity: low Docs Contact:
Priority: low    
Version: 3.5CC: bugs, ebenahar, fromani, gklein, iheim, michal.skrivanek, nsednev, rbalakri, scohen, tnisan, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: ovirt-3.5.1_rc1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-19 07:15:37 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:
Bug Depends On: 1009100    
Bug Blocks: 1145694, 1158049, 1193195    

Description Allon Mureinik 2014-06-08 07:31:34 UTC 
Description of problem:
Some KVM versions on EL do not support Live Snapshots.
If Live Snapshot is not available, Live Storage Migration cannot work, and the operation should be blocked.

bug 1009100 adds the ability to detect this (lack of) support and report it back to the engine. This ability should be utilized in LSM's canDoAction, and possibly in the GUI too.

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

How reproducible:
100%

Steps to Reproduce:
1. Install qemu-kvm (not qemu-kvm-rhev!) on EL6
2. Perform Live Storage Migration

Actual results:
Operation crashes.

Expected results:
Operation should fail elegantly, with a clear CDA message.

Additional info:
Comment 1 Allon Mureinik 2014-08-27 16:11:16 UTC 
Reducing severity and pushing out as we deliver qemu-kvm-rhev in oVirt's channel (see bug 1127763).
Comment 2 Allon Mureinik 2014-11-19 17:57:45 UTC 
*** Bug 1158043 has been marked as a duplicate of this bug. ***
Comment 3 Sandro Bonazzola 2015-01-15 14:15:31 UTC 
This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA