Bug 1382341 - Network is resolved in NetworkAttachment
Summary: Network is resolved in NetworkAttachment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.0.6
: 4.0.6
Assignee: Juan Hernández
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 12:04 UTC by Dominik Holler
Modified: 2017-01-18 07:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-18 07:27:02 UTC
oVirt Team: Network
Embargoed:
juan.hernandez: ovirt-4.0.z?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)
script to reproduce (466 bytes, text/x-python)
2016-10-06 12:04 UTC, Dominik Holler
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 65170 0 master MERGED restapi: Don't populate NetworkAttachment.network.name 2016-10-06 14:16:32 UTC
oVirt gerrit 65177 0 ovirt-engine-4.0 MERGED restapi: Don't populate NetworkAttachment.network.name 2016-10-07 07:50:47 UTC

Description Dominik Holler 2016-10-06 12:04:15 UTC
Created attachment 1207933 [details]
script to reproduce

Description of problem:

Objects of class Network are resolved/populated if a NetworkAttachment is requested by RestAPI, but should not.

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


How reproducible:

Request a NetworkAttachment by RestAPI, see attached check_unresolved_network.py .

Steps to Reproduce:
1. Request a NetworkAttachment by RestAPI
2. Check if the NetworkAttachment's Network is a link or a resolved/populated object

Actual results:

The NetworkAttachment's Network is a resolved/populated object.

Expected results:

The NetworkAttachment's Network is a link to the network object.

Additional info:

Comment 1 Michael Burman 2016-11-21 07:28:10 UTC
Verified on - rhevm-4.0.6-0.1.el7ev.noarch


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