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!
Hi Roman, Do you know how to reproduce this issue on ovn environment without openstack?Thanks!
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.
Created attachment 1582611 [details] contents of ovn nb and sb db tables
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.
(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!
(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.
Verified this bug as sanity only. Job link: https://beaker.engineering.redhat.com/recipes/7023093
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
set qe_test_coverage- as there is no reproducer