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

Bug 1164426

Summary:	The change of boot options should result in the value of Instance Type be changed to custom
Product:	[Retired] oVirt	Reporter:	马立克 <like.ma>
Component:	ovirt-engine-webadmin	Assignee:	Tomas Jelinek <tjelinek>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	ecohen, gklein, iheim, lsurette, mgoldboi, ofrenkel, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.5.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-16 08:48:56 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 马立克 2014-11-15 05:49:14 UTC

Description of problem:
The change of boot options should result in the value of Instance Type be changed to custom.

Version-Release number of selected component (if applicable):
3.5.0.1-1

How reproducible:
always

Steps to Reproduce:
1.Edit a vm whose value of Instance Type is not custom(e.g. Tiny, Small, Medium, Large, XLarge)
2.Select Boot Options tab
3.Change the boot sequence and click ok button
4.Edit the vm again and check the boot sequence

Actual results:
The change has no effect, boot sequence keeps the old value

Expected results:
The boot sequence should be changed successfully and the value of Instance Type should be changed  to custom(it's not the old instance type anymore due to the change of boot sequence)

Additional info:

Comment 1 Omer Frenkel 2014-11-16 08:48:56 UTC

Right, recently there was a thread that it was eventually decided to reduce the list of fields that are mandated by the instance type (please see https://bugzilla.redhat.com/show_bug.cgi?id=1149663#c7 )

so, for this case, it means that even if you are using some instance type, and change the boot order, the selected boot order will apply, instead of changing the instance type to custom.

this should get in 3.5.1 / 3.5.2

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