Bug 1929376 - Warn when creating clone or template from snapshot with memory
Summary: Warn when creating clone or template from snapshot with memory
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.5.3
: ---
Assignee: Lucia Jelinkova
QA Contact: Qin Yuan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 18:36 UTC by Tomáš Golembiovský
Modified: 2022-09-19 14:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-19 14:31:57 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 583 0 None open webadmin: warn when cloning snapshot with memory 2022-08-10 11:10:42 UTC

Description Tomáš Golembiovský 2021-02-16 18:36:41 UTC
It is possible to create clone or a template from snapshot with memory. This is wrong and should not be possible. During the process memory is lost. But when doing memory snapshot the filesystems in guest are not frozen and disk content can be in inconsistent state.

Creating clones or template from memory snapshot should be prohibited.

Comment 1 Arik 2021-02-24 12:55:14 UTC
1. The inconsistency of the file system can also occur when taking a live-snapshot without memory when there's no guest agent installed.
2. This is similar to restore a snapshot that includes memory without restoring its memory in a sense.

Instead of blocking create-vm/template-from-snapshot in that case, we can present a warning as we do in the above mentioned cases to reflect the risk and let the user decide whether to proceed or not.

Comment 2 Casper (RHV QE bot) 2022-09-19 14:31:57 UTC
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.


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