Bug 948775

Summary:	Wrong Boot Options set when creating VM Pool from template using REST API
Product:	[Retired] oVirt	Reporter:	Martin Betak <mbetak>
Component:	ovirt-engine-api	Assignee:	Martin Betak <mbetak>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2	CC:	acathrow, iheim, jkt
Target Milestone:	---
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 07:34:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Betak 2013-04-05 12:05:01 UTC

Description of problem:

When creating a VM Pool from template the boot options for each machine in pool are set to:
Fist device: Hard Disk
Second device: [None]
regardless of what was set as boot options in the template.

Creating the VM Pool from the same template using webadmin gui works correctly.

How reproducible: 

100%

Steps to Reproduce:
1. Create a VM template with non-default boot options (e.g. First device: Network)
2. Create a VM pool from this template using REST API
  
Actual results:

Boot options of VM pool machines are set to Hard Disk, [None]

Expected results:

Boot options of VM pool machines are set to Network, [None] - as specified in the template

Comment 1 Itamar Heim 2013-08-21 16:41:52 UTC

as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 2 Itamar Heim 2013-09-23 07:34:51 UTC

closing as this should be in 3.3 (doing so in bulk, so may be incorrect)