Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2105901

Summary: lsp can't ping it's parent
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Jianlin Shi <jishi>
Component: ovn22.06Assignee: lorenzo bianconi <lorenzo.bianconi>
Status: CLOSED ERRATA QA Contact: Ehsan Elahi <eelahi>
Severity: medium Docs Contact:
Priority: medium    
Version: FDP 22.FCC: ctrautma, eelahi, jiji, lorenzo.bianconi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn22.06-22.06.0-40.el8fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-11 12:25:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jianlin Shi 2022-07-11 06:36:01 UTC
Description of problem:
lsp can't ping it's parent

Version-Release number of selected component (if applicable):
ovn22.06-22.06.0-16.el9

How reproducible:
Always

Steps to Reproduce:
systemctl start openvswitch                                                                           
systemctl start ovn-northd              
ovn-nbctl set-connection ptcp:6641                                       
ovn-sbctl set-connection ptcp:6642                                                                    
ovs-vsctl set open . external_ids:system-id=hv1 external_ids:ovn-remote=tcp:20.0.183.25:6642 external_ids:ovn-encap-type=geneve external_ids:ovn-encap-ip=20.0.183.25
systemctl restart ovn-controller
                                                                                                
ovn-nbctl ls-add ls1
ovn-nbctl lsp-add ls1 ls1p1
ovn-nbctl lsp-set-addresses ls1p1 "00:00:00:01:01:01 192.168.1.1 2001::1"
ovn-nbctl lsp-add ls1 ls1p2
ovn-nbctl lsp-set-addresses ls1p2 "00:00:00:01:01:02 192.168.1.2 2001::2"

ovn-nbctl lr-add lr1
ovn-nbctl lrp-add lr1 lr1-ls1 00:00:00:00:00:01 192.168.1.254/24 2001::a/64
ovn-nbctl lsp-add ls1 ls1-lr1
ovn-nbctl lsp-set-addresses ls1-lr1 "00:00:00:00:00:01 192.168.1.254 2001::a"
ovn-nbctl lsp-set-type ls1-lr1 router
ovn-nbctl lsp-set-options ls1-lr1 router-port=lr1-ls1

ovn-nbctl lrp-add lr1 lr1-ls2 00:00:00:00:00:02 192.168.2.254/24 2002::a/64

ovn-nbctl ls-add ls2
ovn-nbctl lsp-add ls2 ls2-lr1
ovn-nbctl lsp-set-addresses ls2-lr1 "00:00:00:00:00:02 192.168.2.254 2002::a"                                                                                                                               
ovn-nbctl lsp-set-type ls2-lr1 router
ovn-nbctl lsp-set-options ls2-lr1 router-port=lr1-ls2

ovn-nbctl lsp-add ls2 ls2p1
ovn-nbctl lsp-set-addresses ls2p1 "00:00:00:01:02:01 192.168.2.1 2002::1"
ovn-nbctl lsp-add ls2 ls2p2
ovn-nbctl lsp-set-addresses ls2p2 "00:00:00:01:02:02 192.168.2.2 2002::2" 

ovn-nbctl lsp-add ls1 ls1p1_2 ls1p1 2
ovn-nbctl lsp-set-addresses ls1p1_2 "00:00:00:01:01:22 192.168.1.22 2001::22"

ovs-vsctl add-port br-int ls1p1 -- set interface ls1p1 type=internal external_ids:iface-id=ls1p1
ip link add link ls1p1 name ls1p1.2 type vlan id 2
ip netns add ls1p1_2
ip link set ls1p1.2 netns ls1p1_2
ip link set ls1p1 up
ip netns exec ls1p1_2 ip link set ls1p1.2 address 00:00:00:01:01:22
ip netns exec ls1p1_2 ip link set ls1p1.2 up
ip netns exec ls1p1_2 ip addr add 192.168.1.22/24 dev ls1p1.2
ip netns exec ls1p1_2 ip addr add 2001::22/64 dev ls1p1.2

ip link set ls1p1 address 00:00:00:01:01:01
ip link set ls1p1 up
ip addr add 192.168.1.1/24 dev ls1p1
ip addr add 2001::1/64 dev ls1p1

ovn-nbctl --wait=hv sync
ip netns exec ls1p1_2 ping 192.168.1.1 -c 1

Actual results:
+ ovn-nbctl --wait=hv sync
+ ip netns exec ls1p1_2 ping 192.168.1.1 -c 1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.                     
                                                   
--- 192.168.1.1 ping statistics ---                                                                   
1 packets transmitted, 0 received, 100% packet loss, time 0ms

error in ovs-vswitchd.log:

2022-07-11T06:32:29.181Z|00001|ofproto_dpif_xlate(handler43)|INFO|skipping output to input port on bridge br-int while processing ct_state=new|trk,ct_nw_src=192.168.1.22,ct_nw_dst=192.168.1.1,ct_nw_proto=
1,ct_tp_src=8,ct_tp_dst=0,icmp,in_port=1,dl_vlan=2,dl_vlan_pcp=0,vlan_tci1=0x0000,dl_src=00:00:00:01:01:22,dl_dst=00:00:00:01:01:01,nw_src=192.168.1.22,nw_dst=192.168.1.1,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_
type=8,icmp_code=0

Expected results:
ping passed

Additional info:


[root@wsfd-advnetlab18 test]# rpm -qa | grep -E "ovn22.06|openvswitch2.17"
openvswitch2.17-2.17.0-30.el9fdp.x86_64
python3-openvswitch2.17-2.17.0-30.el9fdp.x86_64
ovn22.06-22.06.0-16.el9fdp.x86_64
ovn22.06-central-22.06.0-16.el9fdp.x86_64
ovn22.06-host-22.06.0-16.el9fdp.x86_64

the issue doesn't happen on ovn22.03-22.03.0-62.el9

Comment 2 OVN Bot 2022-08-18 15:17:51 UTC
ovn22.06 fast-datapath-rhel-9 clone created at https://bugzilla.redhat.com/show_bug.cgi?id=2119458

Comment 5 Ehsan Elahi 2022-09-21 14:04:13 UTC
Reproduced on: 
[root@wsfd-advnetlab156 ~]# rpm -qa |grep -E "ovn|openvswitch"
ovn22.06-host-22.06.0-27.el8fdp.x86_64
openvswitch2.17-2.17.0-37.el8fdp.x86_64
ovn22.06-22.06.0-27.el8fdp.x86_64
ovn22.06-central-22.06.0-27.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-29.el8fdp.noarch

Verified on:

[root@wsfd-advnetlab156 ~]# rpm -qa |grep -E "ovn|openvswitch"
openvswitch2.17-2.17.0-37.el8fdp.x86_64
ovn22.06-central-22.06.0-57.el8fdp.x86_64
ovn22.06-host-22.06.0-57.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-29.el8fdp.noarch
ovn22.06-22.06.0-57.el8fdp.x86_64

Also verified on:

[root@wsfd-advnetlab156 ~]# rpm -qa |grep -E "ovn|openvswitch"
ovn22.03-central-22.03.0-95.el8fdp.x86_64
openvswitch2.17-2.17.0-37.el8fdp.x86_64
ovn22.03-host-22.03.0-95.el8fdp.x86_64
ovn22.03-22.03.0-95.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-29.el8fdp.noarch

Comment 7 errata-xmlrpc 2022-10-11 12:25:32 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 (ovn22.06 bug fix and enhancement update), 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-2022:6871