Description of problem:
I have configured OVN L3 logical router for external traffic.
When pinging from VM to the external network or from the external network to the VM, the first time after bringing up ovn l3 router, there is ping loss of the first packet. Afterward, everything works fine even if pinging after
some interval and no packet loss is observed.
basically, if ovn doesn't know the mac for the next hop, it internally sends an arp packet and when it gets ht reply it stores the mac of that IP in mac_binding table so the first packet is dropped.
The issue is just the lack of packet buffering. To fix it, we need to
implement packet buffering somehow.
Version-Release number of selected component (if applicable):
[root@controller-0 ~]# rpm -qa |grep ovn
Steps to Reproduce:
1. boot new vm on ovn setup
2. add to him FIP
3. ping from the external network to the vm you see that the first packet is lost.
the first packet lost
no packet loss
As mentioned in the u/s ML discussions, this is a known limitation and it is by design. It has to be fixed in openvswitch.
Since the fix should to go to openvswitch first, I'm changing the component for this bz.
Updating Target Milestone to z3 for all Modified medium bugs
overcloud) [stack@undercloud-0 ~]$ ssh email@example.com
The authenticity of host '10.0.0.222 (10.0.0.222)' can't be established.
ECDSA key fingerprint is SHA256:RDa93tjACDaE1cZmnNkiPkWGLHYErQDXqwa5ouH1tbk.
ECDSA key fingerprint is MD5:b2:48:bd:78:27:07:a6:ad:1f:b8:ff:91:52:49:6a:ba.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.0.0.222' (ECDSA) to the list of known hosts.
[root@net-64-1-vm-1 ~]# ping 126.96.36.199
PING 188.8.131.52 (184.108.40.206) 56(84) bytes of data.
64 bytes from 220.127.116.11: icmp_seq=1 ttl=116 time=59.4 ms
64 bytes from 18.104.22.168: icmp_seq=2 ttl=116 time=58.7 ms
64 bytes from 22.214.171.124: icmp_seq=3 ttl=116 time=57.9 ms
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.
I am hitting the same issue when I am working with VLAN tenant network type.
Following the above, I see the problem with traffic that goes from External network to the instance
--- 10.46.21.216 ping statistics ---
388 packets transmitted, 386 received, 0% packet loss, time 387044ms
rtt min/avg/max/mdev = 0.413/0.603/1.430/0.103 ms
2 packets lost
Since this bug was shipped on an advisory please clone this bug or file another for failure of issue please.
(In reply to Jon Schlueter from comment #26)
> Since this bug was shipped on an advisory please clone this bug or file
> another for failure of issue please.
np I cloned this issue. https://bugzilla.redhat.com/show_bug.cgi?id=1701893