Bug 1429471

Summary: Difference in REST API behavior on deleting graphic consoles. Display collection disappears.
Product: [oVirt] ovirt-engine Reporter: Vitalii Yerys <vyerys>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.1CC: bugs, sgratch, vyerys
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-07 11:31:35 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 Vitalii Yerys 2017-03-06 12:49:24 UTC 
Description of problem:
When VM becomes headless (All graphic consoles are removed), ​​<display> collection seems to disappear from the VM response body, while <graphics_consoles> collection is represented as empty in VM response body. We have to have the same behavior on this kind of actions.

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

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

How reproducible:
100%

Steps to Reproduce:
1. Delete all consoles from the VM using following REST call (make sure to delete all the consoles):
DELETE ..api/vms/<vm-id>/graphicsconsoles/<console-id>

2. Get the VM description via REST using following call:
GET ..api/vms/<vm-id>
3. Try to find <display> collection.

Actual results:
Collection is not present in the VM Response body

Expected results:
We have to see same behavior on REST calls, basically if graphics consoles are removed and there is an empty <graphics_consoles> collection - there must be a empty <display> collection.


Additional info:
Comment 1 Sharon Gratch 2017-03-07 10:47:42 UTC 
This is just an appearance issue of how the <display> entity is represented in response body in case of headless and since the rest API support wasn't handled for 4.1 (except the /graphicsconsole api) then I guess it will be handled as part of BZ1406394.
Comment 2 Yaniv Kaul 2017-03-07 11:21:09 UTC 
(In reply to Sharon Gratch from comment #1)
> This is just an appearance issue of how the <display> entity is represented
> in response body in case of headless and since the rest API support wasn't
> handled for 4.1 (except the /graphicsconsole api) then I guess it will be
> handled as part of BZ1406394.

Sharon, so can this be closed as duplicate of bug 1406394 ?
Comment 3 Sharon Gratch 2017-03-07 11:26:45 UTC 
(In reply to Yaniv Kaul from comment #2)
> Sharon, so can this be closed as duplicate of bug 1406394 ?
yes, it can be closed as duplicate of bug 1406394.
Comment 4 Sharon Gratch 2017-03-07 11:31:35 UTC 

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