Bug 1390172 - Custom cpu type and emulated machine values are not inherited from instance type to vm when created with API
Summary: Custom cpu type and emulated machine values are not inherited from instance t...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.5.4
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
: ---
Assignee: Tomas Jelinek
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-31 12:07 UTC by sefi litmanovich
Modified: 2022-06-30 08:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-18 09:13:29 UTC
oVirt Team: Virt
sbonazzo: ovirt-4.2-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46766 0 None None None 2022-06-30 08:05:53 UTC

Description sefi litmanovich 2016-10-31 12:07:48 UTC
Description of problem:

When creating via REST API a vm from an instance type which include custom values for cpu type and emulated machine, the vm is created successfully but without these calues (the value is set back to the default None in DB).
When created via webadmin, the values are inherited as expected.

Version-Release number of selected component (if applicable):
rhevm-4.0.5.4-0.1.el7ev

How reproducible:
always

Steps to Reproduce:
1. create/edit an instance type to include some values for system -> custom emulated machine and custom cpu type.
2. Create a vm using API, create from the instance type from (1).


Actual results:
Vm is created, but the values for custom emulated machine and cpu type is None.

Expected results:
Vm is created with the correct values.

Additional info:
no useful information in engine.log

Comment 1 Tomas Jelinek 2017-07-18 09:13:29 UTC
Unfortunately I have to close this due to capacity. Please feel free to reopen it it is important for you.


Note You need to log in before you can comment on or make changes to this bug.