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

Bug 1149663

Summary: Reduce the list of "marked" fields on instance types
Product: Red Hat Enterprise Virtualization Manager Reporter: Bill Sanford <bsanford>
Component: ovirt-engineAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: aberezin, bazulay, benl, dougsland, ecohen, gklein, iheim, like.ma, lpeer, lsurette, mavital, michal.skrivanek, nsimsolo, ofrenkel, pvine, rbalakri, Rhev-m-bugs, tpelka, vipatel, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: org.ovirt.engine-root-3.5.0-23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 08:28:12 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:
Attachments:
Description Flags
Snapshot of changed USB policy and same Instance type none

Description Bill Sanford 2014-10-06 12:25:33 UTC
Description of problem:
When creating a VM in RHEV-M 3.5, in the Console tab, the "Instance Type" is set to anything but "Custom," then you check either the "Soundcard enabled" or "VirtIO Console Device Enabled" and this will reset the "Instance Type" back to "Custom." 

If you select both "Soundcard enabled" and "VirtIO Console Device Enabled" then use the drop-down list to select any "Instance Type" (Except Custom), this will clear both selections of "Soundcard enabled" and "VirtIO Console Device Enabled."

Version-Release number of selected component (if applicable):
RHEV-M 3.5 (vt4/el6)


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomas Jelinek 2014-10-08 07:31:13 UTC
If I understand you correctly, than this is how it is supposed to behave.

1: If you have an instance type selected, than if you select any field which is "marked" (please see the wiki http://www.ovirt.org/Features/Instance_Types - the "marked" column in the table) than the instance type has to change to "custom" - e.g. the VM is not anymore based on the instance type.

2: If you select anything in the dialog and change the instance type, your original selection will be replaced by the instance type's

Comment 2 Bill Sanford 2014-10-09 19:08:57 UTC
I am looking at the http://wiki.ovirt.org/Features/Instance_Types#Design and "usb_policy" is "Marked" in the "VM" section as "Y." This spreadsheet tells me that "Marked: if Y, it means this field is crucial to the instance type definition and if the user changes it, the instance type will change to "custom" (e.g. the VM is not based on that instance type anymore)."

I can change the USB Policy (See attachment) where I chose "Native" USB, in the Console Tab, when it was defaulted to disabled and with the Instance type changed to "Small." 

I see how it works given the nature of the "Profiles" of the new Instance type. I see that the Soundcard and VirtIO are marked Y in the VM section.

I expect that the USB Policy should change the Instance Type back to Custom based on the spreadsheet.

Comment 3 Bill Sanford 2014-10-09 19:19:31 UTC
Created attachment 945429 [details]
Snapshot of changed USB policy and same Instance type

Comment 4 Tomas Jelinek 2014-10-10 10:12:30 UTC
Right, there is a mismatch between the wiki and the behavior. Now the question is if the correct is the wiki or the code. Really not sure about that.

@Michal: what do you think? Should the SPICE USB Policy (native/legacy/disabled) be "marked" so by changing it it detouches the VM from the instance type? Because if you can change the protocol (SPICE/VNC) and also the num of monitors, I'd say also the USB Support should be possible to change.

Comment 5 Michal Skrivanek 2014-10-10 11:15:09 UTC
well, yeah, we have to review it again I think. The minor hw changes should not affect the instance type itself (including soundcard, USB, number of monitors, virtio-console device, I'd say even ballon(device))

Comment 6 Bill Sanford 2014-10-10 11:57:29 UTC
That is why I originally filed the bug. My original thought was that anything that was plug and play on bare metal, should not affect the core of the bare metal, itself and the VM should act the same way. Thanks for reviewing this.

Comment 7 Tomas Jelinek 2014-11-07 08:56:42 UTC
so the new list of "marked" fields will be much smaller:
- memory size
- num of sockets/cores per socket
- HA
- migration model/downtime
- priority
- balloon/min allocated memory

Comment 8 Tomas Jelinek 2014-11-13 13:42:07 UTC
Changed the title according to the discussion in this BZ

Comment 9 Omer Frenkel 2014-11-16 08:48:56 UTC
*** Bug 1164426 has been marked as a duplicate of this bug. ***

Comment 10 Michal Skrivanek 2014-11-26 10:39:48 UTC
one last REST API patch missing backport....

Comment 12 Nisim Simsolo 2014-12-30 10:18:05 UTC
Verified, changes of "Soundcard enabled" and "VirtIO Console Device Enabled" does not change instance type back to custom.
engine build: rhevm-3.5.0-0.27.el6ev.noarch

Comment 13 Omer Frenkel 2015-02-17 08:28:12 UTC
RHEV-M 3.5.0 has been released