Bug 1836976

Summary: [OVN][DVR] Impossible to ping internet addresses from vm with FIP
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Daniel Alvarez Sanchez <dalvarez>
Component: ovn2.13Assignee: lorenzo bianconi <lorenzo.bianconi>
Status: CLOSED ERRATA QA Contact: ying xu <yinxu>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: FDP 20.BCC: apevec, ctrautma, jishi, jlibosva, kfida, lhh, lorenzo.bianconi, majopela, mmichels, ralongi, rsafrono, scohen
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn2.13-2.13.0-33.el7fdn Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1834433 Environment:
Last Closed: 2020-07-15 13:00:54 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: 1834433, 1840605    
Bug Blocks: 1836963, 1836998    

Comment 1 lorenzo bianconi 2020-05-31 22:19:37 UTC
*** Bug 1840605 has been marked as a duplicate of this bug. ***

Comment 4 ying xu 2020-06-08 05:21:14 UTC




ovn-nbctl ls-add network1
		ovn-nbctl lsp-add network1 vm1
		ovn-nbctl lsp-set-addresses vm1 "40:44:00:00:00:01 192.168.0.11"
		ovn-nbctl lsp-add network1 vm2
		ovn-nbctl lsp-set-addresses vm2 "40:44:00:00:00:02 192.168.0.12"

		ovn-nbctl ls-add network2
		ovn-nbctl lsp-add network2 vm3
		ovn-nbctl lsp-set-addresses vm3 "40:44:00:00:00:03 192.168.1.13"

		ovn-nbctl ls-add public
		ovn-nbctl lsp-add public public-localnet
		ovn-nbctl lsp-set-type public-localnet localnet
		ovn-nbctl lsp-set-addresses public-localnet unknown
		ovn-nbctl lsp-set-options public-localnet network_name=external
		ovs-vsctl add-br br-labNet
		ovs-vsctl set Open_vSwitch . external-ids:ovn-bridge-mappings=external:br-labNet
		ovs-vsctl add-port br-labNet ha_veth0
		ip link set br-labNet up

		ovn-nbctl lr-add router1
		ovn-nbctl lrp-add router1 router1-net1 40:44:00:00:00:04 192.168.0.1/24
		ovn-nbctl lsp-add network1 net1-router1
		ovn-nbctl lsp-set-type net1-router1 router
		ovn-nbctl lsp-set-addresses net1-router1 router
		ovn-nbctl lsp-set-options net1-router1 router-port=router1-net1

		ovn-nbctl lrp-add router1 router1-net2 40:44:00:00:00:05 192.168.1.1/24
		ovn-nbctl lsp-add network2 net2-router1
		ovn-nbctl lsp-set-type net2-router1 router
		ovn-nbctl lsp-set-addresses net2-router1 router
		ovn-nbctl lsp-set-options net2-router1 router-port=router1-net2

		ovn-nbctl lrp-add router1 router1-public 40:44:00:00:00:06 172.24.4.1/24
		ovn-nbctl lsp-add public public-router1
		ovn-nbctl lsp-set-type public-router1 router
		ovn-nbctl lsp-set-addresses public-router1 router
		ovn-nbctl lsp-set-options public-router1 router-port=router1-public

		ovn-nbctl --id=@gc0 create Gateway_Chassis name=public-gw1 chassis_name=hv1 priority=20 -- --id=@gc1 create Gateway_Chassis name=public-gw2 chassis_name=hv0 priority=10 -- set Logical_Router_Port router1-public 'gateway_chassis=[@gc0,@gc1]'

		ovn-nbctl lr-nat-add router1 snat 172.24.4.1 192.168.0.0/24
		ovn-nbctl lr-nat-add router1 snat 172.24.4.1 192.168.1.0/24
		ovn-nbctl lr-nat-add router1 dnat_and_snat 172.24.4.100 192.168.0.11 vm1 40:44:00:00:00:07
		ovn-nbctl lr-nat-add router1 dnat_and_snat 172.24.4.101 192.168.0.12 vm2 40:44:00:00:00:08

		ovs-vsctl add-port br-int vm1 -- set interface vm1 type=internal
		ip netns add vm1
		ip link set vm1 netns vm1
		ip netns exec vm1 ip link set lo up
		ip netns exec vm1 ip link set vm1 up
		ip netns exec vm1 ip link set vm1 address 40:44:00:00:00:01
		ip netns exec vm1 ip addr add 192.168.0.11/24 dev vm1
		ip netns exec vm1 ip route add default via 192.168.0.1 dev vm1
		ovs-vsctl set Interface vm1 external_ids:iface-id=vm1

		ovs-vsctl add-port br-int vm2 -- set interface vm2 type=internal
		ip netns add vm2
		ip link set vm2 netns vm2
		ip netns exec vm2 ip link set lo up
		ip netns exec vm2 ip link set vm2 up
		ip netns exec vm2 ip link set vm2 address 40:44:00:00:00:02
		ip netns exec vm2 ip addr add 192.168.0.12/24 dev vm2
		ip netns exec vm2 ip route add default via 192.168.0.1 dev vm2
		ovs-vsctl set Interface vm2 external_ids:iface-id=vm2

		ip netns add external
		ip link add ha_veth0 type veth peer name ha_veth0_p netns external
		ip netns exec external ip link set lo up
		ip netns exec external ip link set ha_veth0_p up
		ip link set ha_veth0 up
		ip netns exec external ip addr add 172.24.4.2/24 dev ha_veth0_p
		ip link add veth0 type veth peer name veth0_peer

		ip link set up dev veth0
		ip link set veth0_peer netns external
		ip netns exec external ip link set up dev veth0_peer
		ip netns exec external ip addr add 192.168.100.1/24 dev veth0_peer
		ip addr add 192.168.100.2/24 dev veth0
		ip route add 172.24.4.0/24 via 192.168.100.1
		ip netns exec external ip route add default via 172.24.4.1
		ip netns exec external sysctl net.ipv4.ip_forward=1

		ovn-nbctl lr-route-add router1 "192.168.100.0/24" 172.24.4.2
reproduced on version:
# rpm -qa|grep ovn
ovn2.13-2.13.0-31.el7fdp.x86_64
ovn2.13-host-2.13.0-31.el7fdp.x86_64
ovn2.13-central-2.13.0-31.el7fdp.x86_64

ping 172.24.4.101 -c 3
PING 172.24.4.101 (172.24.4.101) 56(84) bytes of data.

--- 172.24.4.101 ping statistics ---
3 packets transmitted, 100 received, 100% packet loss

verified on version:
# rpm -qa|grep ovn
ovn2.13-2.13.0-33.el7fdn.x86_64
ovn2.13-host-2.13.0-33.el7fdn.x86_64
ovn2.13-central-2.13.0-33.el7fdn.x86_64


:: [ 23:36:25 ] :: [  BEGIN   ] :: Running 'ping 172.24.4.101 -c 3'
PING 172.24.4.101 (172.24.4.101) 56(84) bytes of data.
64 bytes from 172.24.4.101: icmp_seq=1 ttl=62 time=0.431 ms
64 bytes from 172.24.4.101: icmp_seq=2 ttl=62 time=0.034 ms
64 bytes from 172.24.4.101: icmp_seq=3 ttl=62 time=0.029 ms

--- 172.24.4.101 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.029/0.164/0.431/0.188 ms

Comment 6 errata-xmlrpc 2020-07-15 13:00:54 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-2020:2941