Bug 1548349

Summary: Read-Only Attribute of external network provider is not reported via REST-API
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: RestAPIAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.1.7CC: bugs, mburman
Target Milestone: ovirt-4.2.2Flags: 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: 2018-03-29 11:15:18 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 which get read-only attribute
none
script which get read-only attribute none

Description Dominik Holler 2018-02-23 09:33:43 UTC
Created attachment 1399780 [details]
script which get read-only attribute

Description of problem: The result of getting or updating an OpenStackNetworkProvider does not contain the read-only attribute.


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


How reproducible: Get or Update an OpenStackNetworkProvider via REST-API like in the attached script


Steps to Reproduce:
1. Get or Update an OpenStackNetworkProvider via REST-API
2.
3.

Actual results: The result of getting or updating an OpenStackNetworkProvider does not contain the read-only attribute.


Expected results: The result of getting or updating an OpenStackNetworkProvider does contain the read-only attribute.


Additional info:

Comment 1 Dominik Holler 2018-02-23 09:41:52 UTC
Created attachment 1399783 [details]
script which get read-only attribute

Comment 2 Michael Burman 2018-03-06 14:47:18 UTC
Verified on - 4.2.2.2-0.1.el7

Comment 3 Sandro Bonazzola 2018-03-29 11:15:18 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.