Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1195756 - Need to note that LSM creates a snapshot
Need to note that LSM creates a snapshot
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
3.5.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.5.0
Assigned To: Lucy Bopf
Andrew Burden
:
Depends On:
Blocks: 1193259
  Show dependency treegraph
 
Reported: 2015-02-24 09:01 EST by Allon Mureinik
Modified: 2015-03-12 21:08 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-12 21:08:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Allon Mureinik 2015-02-24 09:01:16 EST
Description of problem:
Section 13.6.3, Moving a Virtual Disk (at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/sect-Virtual_Disk_Tasks.html#Moving_a_Virtual_Machine_Hard_Disk_Between_Data_Domains) clearly documents how to move a disk, and how it will behave during the move.

It's missing, however, a note that states something done the lines of:

"""
Note:
Moving a disk(s) that is connected to a running VM (Live Storage Migration) will automatically create a snapshot for that disk(s).
"""
Comment 1 Andrew Dahms 2015-03-01 23:11:47 EST
Assigning to Lucy for review.
Comment 7 Andrew Burden 2015-03-11 10:40:55 EDT
Looks good. 
'Moving a Virtual Disk' has been updated to include information regarding the automatic creation of a snapshot of a disk as a result of live storage migration. 
Publication spec and Revision History updated.

Rubber Stamp applied.
Comment 8 Lucy Bopf 2015-03-12 21:08:53 EDT
 Included in the latest async release.

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