Bug 1336214 - Implement live merge of auto-generated snapshot and backing file after LSM fails
Summary: Implement live merge of auto-generated snapshot and backing file after LSM fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Ala Hino
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard:
Depends On: 1317434
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-15 18:25 UTC by Ala Hino
Modified: 2016-08-01 12:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This update ensures that the auto-generated snapshot that is created during live storage migration (LSM) is automatically deleted if LSM fails.
Clone Of:
Environment:
Last Closed: 2016-08-01 12:28:25 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.0.0+
ylavi: planning_ack+
amureini: devel_ack+
acanan: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 57843 0 master MERGED lsm: Remove auto-generated snapshot when LSM fails 2016-06-05 08:06:41 UTC
oVirt gerrit 58632 0 ovirt-engine-4.0 MERGED lsm: Remove auto-generated snapshot when LSM fails 2016-06-05 12:39:24 UTC

Description Ala Hino 2016-05-15 18:25:41 UTC
Description of problem:
During live storage migration (LSM), a an auto-generated snapshot is created. BZ 1317434 handled removing the auto-generated snapshot after a successful LSM. This RFE handles removing the auto-generated snapshot after a failure during LSM.

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


How reproducible:
100%

Steps to Reproduce:
1. Start LSM
2. Fail the operation for example by stopping vdsm
3.

Actual results:
Auto-generated snapshot is created and not removed

Expected results:
Auto-generated snapshot to be removed

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2016-05-15 18:27:05 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-15 18:27:05 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Yaniv Lavi 2016-05-23 13:24:41 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 4 Yaniv Lavi 2016-05-23 13:25:54 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Allon Mureinik 2016-06-05 13:22:58 UTC
Ala, this is a highly visible customer facing issue - please provide some doctext for it.

Comment 6 Kevin Alon Goldblatt 2016-07-13 16:48:54 UTC
Verified with the following code:
---------------------------------------
vdsm-4.18.4-2.el7ev.x86_64
rhevm-4.0.2-0.2.rc1.el7ev.noarch

Verified using the following scenario:
---------------------------------------
Create VM with 2 disks
Start the VM
Start the LSM >>> after the auto generated snapshots are created stop the VDSM
After the VDSM starts up again the the LSM completes and the auto generated snapshot is deleted.



Moving to VERIFIED!


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