Bug 1429516 - Different result for UI and REST API action on updating VM with headless resource.
Summary: Different result for UI and REST API action on updating VM with headless reso...
Keywords:
Status: CLOSED DUPLICATE of bug 1406394
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.3
: ---
Assignee: Sharon Gratch
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-06 14:13 UTC by Vitalii Yerys
Modified: 2017-03-07 12:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-07 12:31:55 UTC
oVirt Team: Virt
Embargoed:
tjelinek: ovirt-4.1?
tjelinek: planning_ack?
tjelinek: devel_ack?
tjelinek: testing_ack?


Attachments (Terms of Use)

Description Vitalii Yerys 2017-03-06 14:13:01 UTC
Description of problem:
When the VM is updated with a headless instance_type (no graphic consoles) VM becomes headless (which is okay), but when the same action is performed via REST VM is not transferred to the headless state, and has all of the displays set. The suspicion is that this one is related to BZ1429471.


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

Engine: Red Hat Virtualization Manager Version: 4.1.1-0.1.el7


How reproducible:
100%


Steps to Reproduce:
1. Create a VM.
2. Create a headless instance_type.
3. Update the VM with previously created headless instance type
4. Verify VM becomes headless.
5. Restore VM to setup state (not headless/using some default instance_type)
6. Get the headless instance_type via REST API.
../ovirt-engine/api/instancetypes/<instance_type-id>

7. Update VM to use headless instance_type via Rest by using following call:
PUT ../ovirt-engine/api/vms/<vm-id>

Body:
<vm>
    <response body achieved in step #6>
</vm>

Example of body:
http://pastebin.test.redhat.com/461694


Actual results:
VM is not transferred to headless mode after updating it with headless instance_type via REST API.


Expected results:
The behavior for UI usage and REST API should be the same, and VM should become headless when updating it with headless instance_type.


Additional info:

Comment 1 Sharon Gratch 2017-03-07 11:09:02 UTC
This wasn't meant to be supported for 4.1
The only support we have in REST api for Ovirt 4.1 regarding headless VM/template/instance-type is by using the /graphiccosnoles api for updating an existing such entity to become headless/non-headless.

We still don't support headless by using apis like: 
PUT ../ovirt-engine/api/vms/<vm-id> or 
PUT ../ovirt-engine/api/instancetype/<instance_type-id>

I guess it will be handled as part of BZ1406394 for 4.2

Comment 2 Tomas Jelinek 2017-03-07 12:31:55 UTC
indeed, so lets track it on one place only

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


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