Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1929376

Summary: Warn when creating clone or template from snapshot with memory
Product: [oVirt] ovirt-engine Reporter: Tomáš Golembiovský <tgolembi>
Component: BLL.VirtAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED NEXTRELEASE QA Contact: Qin Yuan <qiyuan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.4CC: ahadas, bugs, dfodor, mzamazal
Target Milestone: ovirt-4.5.3Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-19 14:31:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.