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

Bug 1601713

Summary: Cloning and creating a template from Next Run configuration snapshot is allowed
Product: [oVirt] ovirt-engine Reporter: Eyal Shenitzky <eshenitz>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: futureCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-18 06:27:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eyal Shenitzky 2018-07-17 05:38:01 UTC 
Description of problem:

In case the VM is updated while it is running and the update includes some modification that will take place only while the VM is down, next run configuration snapshot is created for the edited VM.

Currently, the user can create a template and clone a VM from that snapshot.
Those operations should be available only for 'regular' snapshots and should be grayed out / banned in the UI / rest for next run configuration snapshot. 

Version-Release number of selected component (if applicable):
master 3.0 - from the commit 0c772bd3a293e2fdf513f8ceb2002c28fb58d435

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with disk
2. Run the VM
3. Edit the VM to have a lease

Actual results:
Next run configuration snapshot created.
The user can create a template and clone a VM from that snapshot.

Expected results:
Next run configuration snapshot created.
The user cannot create a template and clone a VM from that snapshot.

Additional info:
Comment 1 Michal Skrivanek 2018-07-18 06:27:52 UTC 

*** This bug has been marked as a duplicate of bug 1575913 ***