Bug 1378413 - VM doesn't show it's random generator in REST
Summary: VM doesn't show it's random generator in REST
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 11:07 UTC by jniederm
Modified: 2016-09-22 14:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-22 14:00:26 UTC
oVirt Team: Virt
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
vm.xml (7.15 KB, text/plain)
2016-09-22 11:07 UTC, jniederm
no flags Details

Description jniederm 2016-09-22 11:07:11 UTC
Created attachment 1203685 [details]
vm.xml

Description of problem:
Tag <rng_device> is not show when getting VM with random device assigned.

Version-Release number of selected component (if applicable):
4.1 master, build 50b92e5

How reproducible:
100%

Steps to Reproduce:
1. Make sure random devices are enabled in Cluster
2. Create a VM with random device ("Random Generator" side-tab)
3. GET api/vms/{vmId}

Actual results:
serialized VM not mentioning random device (see attachment)

Expected results:


Additional info:

Comment 1 Juan Hernández 2016-09-22 12:47:54 UTC
The "rng_source" attribute isn't populated unless you include the "All-Content: true" header, as described here:

  https://github.com/oVirt/ovirt-engine-api-model/blob/master/src/main/java/services/VmService.java#L190-L213

That was a design decision, as populating that attribute requires an additional query and thus impacts performance.

Did you include that header in your request?

Comment 2 jniederm 2016-09-22 14:00:26 UTC
No. Thanks for explanation. That solves the problem.


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