[root@dell-per730-19 ovn]# uname -a Linux dell-per730-19.rhts.eng.pek2.redhat.com 3.10.0-1061.el7.x86_64 #1 SMP Thu Jul 11 21:02:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [root@dell-per730-19 ovn]# rpm -qa | grep openvswitch openvswitch-ovn-common-2.9.0-114.el7fdp.x86_64 kernel-kernel-networking-openvswitch-ovn-1.0-130.noarch openvswitch-2.9.0-114.el7fdp.x86_64 openvswitch-ovn-central-2.9.0-114.el7fdp.x86_64 openvswitch-selinux-extra-policy-1.0-13.el7fdp.noarch openvswitch-ovn-host-2.9.0-114.el7fdp.x86_64 [root@dell-per730-19 ovn]# ovn-nbctl show switch 1c85544c-816b-475c-9d91-7a99f24904b1 (s2) port hv1_vm01_vnet1 addresses: ["00:de:ad:01:01:01 172.16.102.12"] port s2_r1 type: router addresses: ["00:de:ad:ff:01:02 172.16.102.1"] router-port: r1_s2 port hv1_vm00_vnet1 addresses: ["00:de:ad:01:00:01 172.16.102.11"] switch c1401fb5-c466-47a8-b88f-d35a9f0689bf (public) port public_r1 type: router router-port: r1_public port ln_p1 type: localnet addresses: ["unknown"] switch 66c76f7a-f63d-4a05-9eb2-3009671b413c (s3) port hv0_vm01_vnet1 addresses: ["00:de:ad:00:01:01 172.16.103.12"] port s3_r1 type: router addresses: ["00:de:ad:ff:01:03 172.16.103.1"] router-port: r1_s3 port hv0_vm00_vnet1 addresses: ["00:de:ad:00:00:01 172.16.103.11"] router 25363a4d-3047-47b6-a7fc-1081bb9b4261 (r1) port r1_public mac: "40:44:00:00:00:03" networks: ["172.16.104.1/24"] port r1_s2 mac: "00:de:ad:ff:01:02" networks: ["172.16.102.1/24"] port r1_s3 mac: "00:de:ad:ff:01:03" networks: ["172.16.103.1/24"] nat 354de591-a1d0-49c0-83a9-3d5704d42bc9 external ip: "172.16.104.200" logical ip: "172.16.102.11" type: "dnat_and_snat" nat 7b71a8b3-a875-4156-9383-700b2e2e7600 external ip: "172.16.104.201" logical ip: "172.16.103.11" type: "dnat_and_snat" [root@dell-per730-19 ovn]# root@dell-per730-19 ovn]# virsh console hv1_vm00 Connected to domain hv1_vm00 Escape character is ^] [root@localhost ~]# [root@localhost ~]# ping -c3 172.16.104.201 PING 172.16.104.201 (172.16.104.201) 56(84) bytes of data. 64 bytes from 172.16.104.201: icmp_seq=1 ttl=63 time=1.84 ms 64 bytes from 172.16.104.201: icmp_seq=2 ttl=63 time=0.296 ms 64 bytes from 172.16.104.201: icmp_seq=3 ttl=63 time=0.349 ms --- 172.16.104.201 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.296/0.829/1.842/0.716 ms [root@localhost ~]# [root@dell-per730-57 ovn]# tcpdump -ei p4p2 | grep 172.16 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on p4p2, link-type EN10MB (Ethernet), capture size 262144 bytes 04:43:35.056775 00:00:00:01:02:03 (oui Ethernet) > 00:00:00:04:05:06 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo request, id 11675, seq 1, length 64 04:43:35.057330 00:00:00:04:05:06 (oui Ethernet) > 00:00:00:01:02:03 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo reply, id 11675, seq 1, length 64 04:43:36.058168 00:00:00:01:02:03 (oui Ethernet) > 00:00:00:04:05:06 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo request, id 11675, seq 2, length 64 04:43:36.058290 00:00:00:04:05:06 (oui Ethernet) > 00:00:00:01:02:03 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo reply, id 11675, seq 2, length 64 04:43:37.058531 00:00:00:01:02:03 (oui Ethernet) > 00:00:00:04:05:06 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.200 > 172.16.104.201: ICMP echo request, id 11675, seq 3, length 64 04:43:37.058711 00:00:00:04:05:06 (oui Ethernet) > 00:00:00:01:02:03 (oui Ethernet), ethertype 802.1Q (0x8100), length 102: vlan 4, p 0, ethertype IPv4, 172.16.104.201 > 172.16.104.200: ICMP echo reply, id 11675, seq 3, length 64
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:2529