Created attachment 1271287 [details] engine and vdsm logs Description of problem: When previewing a snapshot with more than 1 disk, and selecting the first option in the "Preview partial snapshot" dialog box (screenshot attached): "Include in the previewed VM all disks (keep the disks that are not included in the snapshot as-is)." The operation creates a copy of every VM disk. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a VM with 2 disks 2. Create a snapshot include the 2 VM disks 3. Preview the snapshot and select the first option Actual results: Every VM disk now appears twice (there are 2 bootable disks and every operation on one disk, applies on its copy too) Expected results: No exceptions in engine.log Additional info: The snapshot creation start at: 2017-04-13 01:07:04,610+03 INFO [org.ovirt.engine.core.bll.snapshots.CreateAllSnapshotsFromVmCommand] (org.ovirt.thread.pool-7-thread-15) [e2e96bee-f0ec-4060-b367-5118c1479271] Running command: CreateAllSnapshotsFromVmCommand internal: false. Entities affected : ID: d23ef003-8c3e-42b2-bc92-599379af98f4 Type: VMAction group MANIPULATE_VM_SNAPSHOTS with role type USER
Created attachment 1271289 [details] screenshot_preview
Not sure why it's high severity. Is that a regression?
Yes, it is a regression - keyword added
Raz, given the version you've set I guess you tested it on master, can you please try and see if it reproduces on a 4.1 environment?
Version-Release number of selected component (if applicable): oVirt Engine Version: 4.2.0-0.0.master.20170408115943.gitea6bd62.el7.centos Already tested on 4.1 and this doesn't happen there
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.
Verified on ovirt-4.2.0-0.0.master.20170519193842.gitf4353fb6.el7.centos Preview snapshot work as expected
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.