Bug 1332489

Summary: Creating a new VM from a template's context menu doesn't copy initial run parameters
Product: Red Hat Enterprise Virtualization Manager Reporter: Eric Lavarde <elavarde>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.5CC: gklein, lsurette, michal.skrivanek, rbalakri, Rhev-m-bugs, srevivo, tjelinek, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-04 08:38:40 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:

Description Eric Lavarde 2016-05-03 10:37:10 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
 Red Hat Enterprise Virtualization Manager Version: 3.6.5.3-0.1.el6 

How reproducible:
Always

Steps to Reproduce:
1. Create a template where the "Initial Run -> Cloud Init / Sysprep" parameters are set.
2. Right-Click on the Template -> "New VM"
3. Go to Tab "Initial Run"

Actual results:

The Cloud Init parameters are lost (there might be other parameters impacted but I couldn't find any)

Expected results:

The Cloud Init parameters are still present and pre-populated as in the template.

Additional info:

If I go to the "General" tab and reselect explicitly the "Template" field value then the Initial Run and Cloud Init / Sysprep fields are properly populated (which is an acceptable workaround, hence the low priority).
Comment 1 Tomas Jelinek 2016-05-04 08:38:40 UTC 
This has already been fixed for 4.0 - https://bugzilla.redhat.com/show_bug.cgi?id=1328463

Marking as duplicate.

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