Bug 1378902 - vv file can't be obtained using SDK
Summary: vv file can't be obtained using SDK
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.0-beta
: 4.1.0.2
Assignee: Ondra Machacek
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 13:22 UTC by jniederm
Modified: 2017-02-15 14:59 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-15 14:59:17 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
mperina: devel_ack+
mavital: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 65721 0 master MERGED restapi: Add remoteviewerconnectionfile action to graphicsconsole 2017-01-14 12:24:27 UTC
oVirt gerrit 65723 0 None None None 2016-10-27 07:38:55 UTC
oVirt gerrit 70347 0 ovirt-engine-4.1 MERGED restapi: Add remoteviewerconnectionfile action to graphicsconsole 2017-01-14 21:19:49 UTC

Description jniederm 2016-09-23 13:22:34 UTC
Description of problem:
Request
GET /ovirt-engine/api/vms/fbdce5c4-d20f-43e0-b40b-67a1f7ca06d2/graphicsconsoles/7370696365 HTTP/1.1
Host: ...
Authorization: Basic ...
(without explicit "Accept" header or with Accept: application/x-virt-viewer) directly returns vv file content whereas sdk returns standard object. 

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

How reproducible:
100%

Steps to Reproduce:
In [39]: spice_service.get()
Out[39]: <ovirtsdk4.types.GraphicsConsole at 0x7f5f2d4a2110>          

In [40]: dir(spice_service.get())
Out[40]: 
['__class__',
 '__delattr__',
 '__dict__',
 '__doc__',
 '__format__',
 '__getattribute__',
 '__hash__',
 '__init__',
 '__module__',
 '__new__',
 '__reduce__',
 '__reduce_ex__',
 '__repr__',
 '__setattr__',
 '__sizeof__',
 '__str__',
 '__subclasshook__',
 '__weakref__',
 '_address',
 '_check_type',
 '_comment',
 '_description',
 '_href',
 '_id',
 '_instance_type',
 '_name',
 '_port',
 '_protocol',
 '_template',
 '_tls_port',
 '_vm',
 'address',
 'comment',
 'description',
 'href',
 'id',
 'instance_type',
 'name',
 'port',
 'protocol',
 'template',
 'tls_port',
 'vm']


Actual results:


Expected results:
There is some way (probably method of GraphicsConsole) allowing to obtain content of vv file.

Additional info:

Comment 1 Martin Perina 2016-10-11 12:39:14 UTC
After discussion with Ondra moving to ovirt-engine (as this will be backend change) and targeting to 4.1

Comment 2 Ondra Machacek 2016-10-27 10:17:54 UTC
In order to test this please follow this example:

 https://{enginefqdn}/ovirt-engine/api/model#types/graphics_console/attributes/remote_viewer_connection_file

Comment 3 Israel Pinto 2017-02-10 15:23:24 UTC
Verify with REST and python sdk 
Engine:
Red Hat Virtualization Manager Version: 4.1.0.3-0.1.el7


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