Bug 1506697 - Don't freeze the VM when taking a live snapshot in LSM
Summary: Don't freeze the VM when taking a live snapshot in LSM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Benny Zlotnik
QA Contact: Lilach Zitnitski
URL:
Whiteboard:
Depends On:
Blocks: 1557448
TreeView+ depends on / blocked
 
Reported: 2017-10-26 15:10 UTC by Allon Mureinik
Modified: 2018-03-19 12:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:32:36 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 84016 0 'None' MERGED core: do not freeze FS when creating the LSM snapshot 2020-05-31 11:20:56 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.