This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
The problem with spice reproduce, can't open spice after start the vm with the preview memory snapshot. Dialog window error: Error while executing action SetVmTicket: Unexpected exception envent log: 2015-Nov-05, 14:43: user admin@internal failed to initiate a console session for VM test Steps to Reproduce: 1. Create a VM with an OS, start it, make a snapshot and stop it. 2. start the vm and start a process (in my example: cat /dev/zero) 2. Create a RAM snapshot 3. Shutdown the vm 5. Preview the RAM snapshot 6. Start the vm with the preview snapshot Setup: Engine:3.5.6.2-0.1.el6ev VDSM:vdsm-4.16.27-1.el7ev libvirt:libvirt-1.2.17-13.el7 spice: 0.12.4 - 15.el7 reopening the bug, adding logs
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.
Created attachment 1090137 [details] snapshot_log_engine_vdsm_qemu
Unfortunately the fix didn't make in time for 4.16.27 and was merged in 4.16.28. So it is definitely true that the bug still reproduces with VDSM < 4.16.28. Please retry using VDSM >= 4.16.28. Moving back to MODIFIED.
not a blocker and no respin is planned, moving to 3.5.7
(In reply to Francesco Romani from comment #7) > Unfortunately the fix didn't make in time for 4.16.27 and was merged in > 4.16.28. > So it is definitely true that the bug still reproduces with VDSM < 4.16.28. > Please retry using VDSM >= 4.16.28. > > Moving back to MODIFIED. it seems comment 4 was an incorrect setup, the right vdsm is indeed in vt18.2
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
(In reply to Red Hat Bugzilla Rules Engine from comment #10) > Bug tickets that are moved to testing must have target release set to make > sure tester knows what to test. Please set the correct target release before > moving to ON_QA. AAAAAARGH!
Verify with: Setup: Engine:3.5.6.2-0.1.el6ev VDSM: vdsm-4.16.29-1.el7ev.x86_64 libvirt: libvirt-1.2.17-13.el7 spice: 0.12.4 - 15.el7 Steps to Reproduce: 1. Create a VM with an OS, start it, make a snapshot and stop it. 2. start the vm and start a process (in my example: cat /dev/zero) 2. Create a RAM snapshot 3. Shutdown the vm 5. Preview the RAM snapshot 6. Start the vm with the preview snapshot 7. Start spice Results: Pass
*** Bug 1278011 has been marked as a duplicate of this bug. ***
oVirt 3.5.6 has been released and the bz verified, moving to closed current release.