yahoo-eng-team team mailing list archive

[OpenStack Infra <1566951@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/611059
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1966ad3945a7a44beeefc603f9d6da54ac67f9a3
Submitter: Zuul
Branch:    master

commit 1966ad3945a7a44beeefc603f9d6da54ac67f9a3
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Fri Nov 2 11:35:25 2018 +0000

    Check port VNIC type when associating a floating IP
    
    When associating a floating IP to a port and the router is distributed,
    the VNIC type of this port must be "normal" only. In any other case,
    the floating IP can't be assigned. For example, a SR-IOV can have a
    floating IP if the router is distributed (the router is in the same
    host of the port).
    
    Closes-Bug: #1566951
    
    Change-Id: I4944041df81e24683bc612560808bcdcc2db6bf2


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1566951

Title:
  Duplicated traffic in SR-IOV and DVR mode

Status in Mirantis OpenStack:
  Won't Fix
Status in Mirantis OpenStack 10.0.x series:
  Confirmed
Status in neutron:
  Fix Released

Bug description:
  Detailed bug description:
   On DVR VLAN env vm with SR-IOV has duplicated traffic during pin external host or internal ip 

  Steps to reproduce:
  1. Deployed env with SR-IOV and DVR
  2. Create net1, subnet
  3. Create net2, subnet
  4. Create DVR router, set gatawey, add interface for both nets
  5. Create sr-iov port in net1 (port_sriov_1)
  6. Create sr-iov port in net2 (port_sriov_2)
  7. Boot ubuntu vm1 with port port_sriov_1
  8. Boot ubuntu vm 2with port port_sriov_2
  9. Associate floating for vm1
  10. Ping from vm1 8.8.8.8, ping vm2 by floating

  Expected results:
   Ping is available, packets are not duplicated

  Actual result:
  Packets are duplicated:
  ubuntu@vm-ew-1:~$ ping 10.1.2.6
  PING 10.1.2.6 (10.1.2.6) 56(84) bytes of data.
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.312 ms
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.313 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.314 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.315 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)
  64 bytes from 10.1.2.6: icmp_seq=1 ttl=63 time=0.316 ms (DUP!)

  ubuntu@vm-ew-1:~$ ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=5.41 ms (DUP!)
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=4.36 ms

  Description of the environment:
  Find on iso 155, vlan+dvr+enable sr-iov

  Additional information:
   I boot usual vm in net1 and ping 8.8.8.8 work good

To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1566951/+subscriptions