Bug 1083697 - [engine-backend] [RAM snapshot] preview snapshot to RAM shouldn't be allowed if the memory image cannot be accessed
Summary: [engine-backend] [RAM snapshot] preview snapshot to RAM shouldn't be allowed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: ---
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Arik
QA Contact:
URL:
Whiteboard:
Depends On: 1150239
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-02 18:31 UTC by Elad
Modified: 2022-07-01 12:35 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-03-10 10:56:15 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)
logs from engine and host (1.29 MB, application/x-gzip)
2014-04-02 18:31 UTC, Elad
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46920 0 None None None 2022-07-01 12:35:05 UTC

Description Elad 2014-04-02 18:31:47 UTC
Created attachment 881949 [details]
logs from engine and host

Description of problem:
If a storage domain contains an image of RAM snapshot and the domain is in inactive state, preview snapshot to the VM is allowed. 

Version-Release number of selected component (if applicable):
rhevm-3.4.0-0.12.beta2.el6ev.noarch
vdsm-4.14.5-0.2.beta2.el6ev.x86_64

How reproducible:
Always

Steps to Reproduce:
On a DC (local/shared) with more than 1 storage domains:
1. Create a VM and run it
2. Create snapshot to the VM with RAM saved
3. Shut down the VM
4. Put the storage domain where the RAM image was saved to in maintenance
5. Try to preview the snapshot with the RAM 


Actual results:
Snapshot preview with RAM is allowed, even though the RAM image cannot be accessed since the storage domain where it is located is inactive.
When starting this VM with the snapshot pre-viewed, the RAM Memory restore fails.

2014-04-02 17:45:41,118 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-48) Rerun vm 280e0ee1-ad2f-4234-9d7a-5908d020ce43. Called fro
m vds green-vdsb


Expected results:
If RAM memory image cannot be accessed, snapshot preview with RAM memory should not be allowed. It should be the same behaviour as previewing a snapshot which its data disk cannot be accessed.
 

Additional info: logs from engine and host

Comment 1 Michal Skrivanek 2014-08-22 13:01:39 UTC
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know

Comment 2 Omer Frenkel 2015-09-08 07:43:02 UTC
It would make more sense to solve this after we re-implement the memory volumes as disks, see bug 1150239

Comment 3 Red Hat Bugzilla Rules Engine 2015-11-30 19:01:58 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Yaniv Kaul 2016-03-10 10:56:15 UTC
Closing old tickets, in medium/low severity. If you believe it should be re-opened, please do so and add justification.


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