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

Bug 1102783

Summary: [engine-backend] When committing a snapshot that contains disk and conf. of the 'Active VM', engine doesn't report about the result of the operation
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: acathrow, amureini, gickowic, gklein, iheim, lpeer, Rhev-m-bugs, scohen, tpoitras, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 3.4.1   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, attempting to preview and commit the configuration file and disks of an active virtual machine would show that that the operation had started, but the results were never reported. Now, previewing an active virtual machine snapshot has been blocked.
 Story Points: ---
Clone Of: 1096884 Environment:
Last Closed: 2014-07-29 16:23:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1096884    
Bug Blocks:    

Comment 2 Aharon Canan 2014-06-30 14:11:17 UTC 
verified using av10

"vm01:

    Cannot preview Active VM snapshot"

verification -
1. create a snapshot for VM with disk
2. custom preview the active VM and active disk
3. click "ok' - get the warning message
Comment 3 Gadi Ickowicz 2014-06-30 14:59:40 UTC 
tested using RESTAPI as well - attempting to preview Active VM snapshots returns the following message:

...
    <fault>
        <reason>Operation Failed</reason>
        <detail>[Cannot preview Active VM snapshot.]</detail>
    </fault>
...
Comment 5 errata-xmlrpc 2014-07-29 16:23:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0960.html