Bug 1805142

Summary: Updating an OpenStack port creates invalid json
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: Backend.CoreAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, dfodor, mduarted
Target Milestone: ovirt-4.4.0Flags: pm-rhel: ovirt-4.4+
dholler: blocker?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:00: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
logfiles, including ovirt-provider-ovn.log and engine.log none

Description Dominik Holler 2020-02-20 11:04:52 UTC
Created attachment 1664314 [details]
logfiles, including ovirt-provider-ovn.log and engine.log

Description of problem:
If engine tries to update an OpenStack port, the generated json misses the "port" root element.

Version-Release number of selected component (if applicable):
ovirt-engine.noarch 4.4.0-0.0.master.20200218121717.git14967178f54.el8

How reproducible:
100%

Steps to Reproduce:
network-suite-master.tests.ovn-provider.test_ovn_provider_integration_with_ovirt.test_modify_vnic_sec_groups_on_ext_networks

Actual results:
updating a port fails

Expected results:
updating a port works

Additional info:
The issue might be introduced by updating
openstack-java-sdk-3.2.7
to
openstack-java-sdk-3.2.8

Comment 3 Michael Burman 2020-03-17 10:12:28 UTC
Verified on - rhvm-4.4.0-0.25.master.el8ev.noarch with
openstack-java-*-3.2.8-1.el8ev.noarch
ovirt-provider-ovn-1.2.29-1.el8ev.noarch
ovn2.11-2.11.1-33.el8fdp.x86_64
openvswitch2.11-2.11.0-48.el8fdp.x86_64
rhel 8.2

Comment 4 Sandro Bonazzola 2020-05-20 20:00:18 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.