Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1548348

Summary: Updating external network provider via REST-API overwrites additionalProperties with default values
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 10:57:25 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 should set read_only to False
none
script which should set read_only to False none

Description Dominik Holler 2018-02-23 09:27:52 UTC
Created attachment 1399779 [details]
script which should set read_only to False

Description of problem: On updating an OpenStackNetworkProvider, additionalProperties, e.g. read_only, are overwritten by default values instead of using the previous values.


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


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


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

Actual results: Not updated additionalProperties like read_only are reset to default values.


Expected results: Not updated AdditionalProperties like read_only should remain the same value as before the update.


Additional info:

Comment 1 Dominik Holler 2018-02-23 09:42:23 UTC
Created attachment 1399793 [details]
script which should set read_only to False

Comment 2 Michael Burman 2018-03-06 15:30:32 UTC
Verified on - 4.2.2.2-0.1.el7

Comment 3 Sandro Bonazzola 2018-03-29 10:57:25 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.