[NETVIRT-144] first few ping requests to a floating IP are receiving multiple responses Created: 14/Sep/16  Updated: 05/Oct/16  Resolved: 05/Oct/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Koby Aizer Assignee: Olga Schukin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6721

 Description   

In this scenario there are 3 computes, and 10.80.5.14 is a floating IP.
The first few ping requests were receiving multiple responses. Assumption is that multiple computes were somehow forwarding those packets.

I lost the dump-flows of the setup, but should be trivial to reproduce.

$ ping 10.80.5.14
PING 10.80.5.14 (10.80.5.14) 56(84) bytes of data.
64 bytes from 10.80.5.14: icmp_seq=1 ttl=63 time=4.90 ms
64 bytes from 10.80.5.14: icmp_seq=1 ttl=63 time=4.92 ms (DUP!)
64 bytes from 10.80.5.14: icmp_seq=1 ttl=63 time=4.93 ms (DUP!)
64 bytes from 10.80.5.14: icmp_seq=2 ttl=63 time=0.197 ms
64 bytes from 10.80.5.14: icmp_seq=3 ttl=63 time=0.380 ms

 Comments   
Comment by Andre Fredette [ 19/Sep/16 ]

I'm seeing this with 2 compute nodes:

$ ping www.google.com
PING www.google.com (172.217.2.4): 56 data bytes
64 bytes from 172.217.2.4: seq=0 ttl=61 time=35.026 ms
64 bytes from 172.217.2.4: seq=0 ttl=61 time=36.730 ms (DUP!)
64 bytes from 172.217.2.4: seq=1 ttl=61 time=35.804 ms
64 bytes from 172.217.2.4: seq=1 ttl=61 time=40.100 ms (DUP!)
64 bytes from 172.217.2.4: seq=2 ttl=61 time=41.355 ms
64 bytes from 172.217.2.4: seq=2 ttl=61 time=47.575 ms (DUP!)

Any update? Thanks.

Comment by Olga Schukin [ 27/Sep/16 ]

Vivekanandan Narasimhan's review:
https://git.opendaylight.org/gerrit/#/c/46096/

Generated at Wed Feb 07 20:20:49 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.