Bug 1382341

Summary: Network is resolved in NetworkAttachment
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: RestAPIAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.0.1CC: bugs, mburman
Target Milestone: ovirt-4.0.6Flags: juan.hernandez: ovirt-4.0.z?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 4.0.6   
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-01-18 07:27:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
script to reproduce none

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