Bug 1261102 - When previewing snapshot without memory floppy device is lost
Summary: When previewing snapshot without memory floppy device is lost
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Arik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-08 15:05 UTC by Jiri Belka
Modified: 2022-05-16 07:47 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-21 07:43:36 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.2-

Attachments (Terms of Use)
engine.log, vdsm.log, libvirt/qemu/$vm.log (968.03 KB, application/x-gzip)
2015-09-08 15:05 UTC, Jiri Belka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46046 0 None None None 2022-05-16 07:47:14 UTC

Description Jiri Belka 2015-09-08 15:05:02 UTC 
Created attachment 1071391 [details]
engine.log, vdsm.log, libvirt/qemu/$vm.log

Description of problem:
When previewing snapshot without memory floppy device is lost. When previewing include memory everything works ok.

Version-Release number of selected component (if applicable):
rhevm-backend-3.6.0-0.13.master.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run Once a VM with attached floppy
2. make snapshot
3. power off the VM
4. preview the snapshot without memory
5. click Run button

Actual results:
floppy is lost

Expected results:
should be there

Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2015-11-30 19:15:41 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 2 Moran Goldboim 2016-03-27 08:10:37 UTC 
Postponing for next version due to capacity.
Comment 3 Michal Skrivanek 2016-12-21 09:08:29 UTC 
The bug was not addressed in time for 4.1. Postponing to 4.2
Comment 4 Michal Skrivanek 2017-08-21 07:43:36 UTC 
we didn't get to it for 2 years and it doesn't sound like a very interesting case. Closing
Note You need to log in before you can comment on or make changes to this bug.