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

Bug 1323780

Summary: Cannot create a stateless vm from 'latest' template version if template is not stateless
Product: [oVirt] ovirt-engine Reporter: sefi litmanovich <slitmano>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED WONTFIX QA Contact: sefi litmanovich <slitmano>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.5.1CC: bugs, tjelinek
Target Milestone: ---Flags: sbonazzo: ovirt-4.2-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-18 08:55:50 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 sefi litmanovich 2016-04-04 16:56:25 UTC
Description of problem:

User should be able to create a vm from some template and amend some configurations if he likes. In particular user should able to create a stateless vm based on 'latest' template version so the vm can update according to template versions. Right now due to the change introduced in bz#1293154 this cannot be achieved if the latest template is not configured as stateless itself.
While this is not a major issue and can be rather easily WA by editing the template, this should be changed so that when a user chooses 'stateless' on the create vm menu and then some latest template is chosen, it will not override the stateless configuration.

Version-Release number of selected component (if applicable):
rhevm-3.6.5.1-0.1.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Create template from some statefull vm.
2. Attempt to create a new vm -> set stateless check-box. 
3. In Create vm->general menu choose the template you created as 'latest' version in the template drop down.

Actual results:
Vm inherits template's configuration and set back to statefull, vm's template is set to base template version (1).

Expected results:
Vm inherits should inherit template's configuration except for the stateless, allowing to create the vm as stateless, with latest template version, regardless to the template statefullness.

Additional info:

Comment 1 Tomas Jelinek 2016-04-05 06:11:12 UTC
The work around is to set the latest template to be stateless.

Comment 2 Michal Skrivanek 2016-12-21 09:09:29 UTC
The bug was not addressed in time for 4.1. Postponing to 4.2

Comment 3 Tomas Jelinek 2017-07-18 08:55:50 UTC
The workaround is easy.

Unfortunately I have to close this due to capacity. If it is an important item for you, please feel free to reopen.