Bug 1506697

Summary:	Don't freeze the VM when taking a live snapshot in LSM
Product:	[oVirt] ovirt-engine	Reporter:	Allon Mureinik <amureini>
Component:	BLL.Storage	Assignee:	Benny Zlotnik <bzlotnik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lilach Zitnitski <lzitnits>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	bugs, trichard
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Virtual machine file systems are no longer frozen while taking the temporary snapshots created during live storage migration. This improves the speed of the migration.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:32:36 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:
Bug Blocks:	1557448

Description Allon Mureinik 2017-10-26 15:10:11 UTC

Description of problem:
The live snapshot taken in LSM is temporary, and is merged into once LSM is done. There's no point in freezing the VM when taking it.

This is currently controlled in org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand#shouldFreezeOrThawVm

Comment 1 Lilach Zitnitski 2017-12-12 12:56:38 UTC

--------------------------------------
Tested with the following code:
----------------------------------------
rhvm-4.2.0-0.6.el7.noarch
vdsm-4.20.9-1.el7ev.x86_64

Tested with the following scenario:

Steps to Reproduce:
1. start LSM 


Actual results:
Guest's file system did not freeze during the LSM 

Expected results:

Moving to VERIFIED!

Comment 2 Sandro Bonazzola 2017-12-20 11:32:36 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.