Bug 1706870

Summary: [OVN] Exception on attempt to create an instance connected to public network
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Timothy Redaelli <tredaelli>
Component: openvswitchAssignee: Timothy Redaelli <tredaelli>
openvswitch sub component: other QA Contact: haidong li <haili>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: apevec, atragler, chrisw, ctrautma, fhallal, jishi, lhh, lmartins, majopela, nusiddiq, pvauter, qding, ragiman, rbryant, rhos-maint, rsafrono, scohen, tredaelli
Version: FDP 18.11   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvswitch-2.9.0-107.el7fdn Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1703740 Environment:
Last Closed: 2019-07-10 12:57:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1703740    
Attachments:
Description Flags
contents of ovn nb and sb db tables none

Comment 2 haidong li 2019-06-14 02:26:17 UTC
Hi Timothy,
   I can't get how to reproduce the issue with ovn commands.Can you please help show the steps to reproduce this issue on OVN? Thanks a lot!

Comment 4 haidong li 2019-06-20 03:24:46 UTC
Hi Roman,
   Do you know how to reproduce this issue on ovn environment without openstack?Thanks!

Comment 5 Roman Safronov 2019-06-20 10:01:58 UTC
Hi Haidong,

No I don't know how to reproduce without openstack. Here is output of ovn-nbctl show command. vm connected to a logical switch port.

[root@compute-1 ~]# nb show
switch 2f9e31aa-3195-4436-91ee-3da77c5afdde (neutron-3891a2b1-aa9f-4b7d-b78a-e1ee49955b10) (aka public)
    port provnet-3891a2b1-aa9f-4b7d-b78a-e1ee49955b10
        type: localnet
        addresses: ["unknown"]
    port ba4f5d7d-64b5-4a97-a52c-f554cbdda3cd
        addresses: ["fa:16:3e:48:03:0f 10.0.0.231"]

I also attach output of other commands displaying ovn db contents.

Comment 6 Roman Safronov 2019-06-20 10:02:49 UTC
Created attachment 1582611 [details]
contents of ovn nb and sb db tables

Comment 7 Numan Siddique 2019-06-20 18:22:27 UTC
Hi Haidong Li,

The issue is in the ovs python IDL client code. Openstack networking-ovn code uses the ovs python IDL code. So you will not be able to reproduce this issue just with core OVN.

Comment 8 haidong li 2019-06-21 09:17:08 UTC
(In reply to Numan Siddique from comment #7)
> Hi Haidong Li,
> 
> The issue is in the ovs python IDL client code. Openstack networking-ovn
> code uses the ovs python IDL code. So you will not be able to reproduce this
> issue just with core OVN.

Hi Numan,
  Thank you for reminding this.So I don't have to test this with core OVN,I will try to check the python code.Thanks a lot!

Comment 9 haidong li 2019-06-21 09:23:41 UTC
(In reply to Roman Safronov from comment #5)
> Hi Haidong,
> 
> No I don't know how to reproduce without openstack. Here is output of
> ovn-nbctl show command. vm connected to a logical switch port.
> 
> [root@compute-1 ~]# nb show
> switch 2f9e31aa-3195-4436-91ee-3da77c5afdde
> (neutron-3891a2b1-aa9f-4b7d-b78a-e1ee49955b10) (aka public)
>     port provnet-3891a2b1-aa9f-4b7d-b78a-e1ee49955b10
>         type: localnet
>         addresses: ["unknown"]
>     port ba4f5d7d-64b5-4a97-a52c-f554cbdda3cd
>         addresses: ["fa:16:3e:48:03:0f 10.0.0.231"]
> 
> I also attach output of other commands displaying ovn db contents.

Hi Roman,
   Thanks for your help and the detailed information,I will check them.I think I will test this bug with sanity only.

Comment 10 haidong li 2019-06-24 05:37:04 UTC
Verified this bug as sanity only.
Job link:
https://beaker.engineering.redhat.com/recipes/7023093

Comment 12 errata-xmlrpc 2019-07-10 12:57:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2019:1748

Comment 13 Jianlin Shi 2019-11-08 06:18:41 UTC
set qe_test_coverage- as there is no reproducer