yahoo-eng-team team mailing list archive

[OpenStack Infra <1870114@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/716642
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d0a16522272bce64bceca1ccdb8d98a38d953cf5
Submitter: Zuul
Branch:    master

commit d0a16522272bce64bceca1ccdb8d98a38d953cf5
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Tue Mar 31 20:39:13 2020 +0200

    Add trunk subports to be one of dvr serviced device owners
    
    When "trunk:subport" wasn't added to the list of device owners which
    are supported by dvr, there was no proper config in br-int's openflow
    rules for such port, e.g. there was no dvr_to_src_mac rule in table 1
    added and traffic from such port was never going through br-int.
    
    Trunk ports should be added to this dvr serviced device owners list and
    that patch is adding it there.
    
    Change-Id: Ic21089adfa32dbf5d0e29a89713e6e2bf28f0f05
    Closes-Bug: #1870114


** 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/1870114

Title:
  Trunk subports aren't treated as dvr serviced ports

Status in neutron:
  Fix Released

Bug description:
  In case of dvr, for dvr serviced ports, there are openflow rules in
  br-int installed to translate port's mac address to gateway mac. It's
  in table 1 of br-int and it looks like:

  cookie=0xf8f0be9a44e579e7, duration=351.138s, table=1, n_packets=0,
  n_bytes=0, idle_age=353,
  priority=20,dl_vlan=3,dl_dst=fa:16:3e:94:c3:a5
  actions=mod_dl_src:fa:16:3e:48:5e:70,resubmit(,60)

  But trunk subports aren't included in list of dvr serviced device
  owners so traffic from those ports isn't going through those rules and
  it never goes out of the br-int.

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