← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1899967] Re: L3HA Router in primary state on all nodes

 

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

commit 14a1ad7009fb20f21bf58accbd339264bebed3b9
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Sat Oct 24 08:27:38 2020 +0000

    Revert "Process ingress multicast traffic for 224.0.0.X separately"
    
    This reverts commit b8be1a05facff2ba8b484902494ce1663e0aae7c.
    
    As was reported in bug [1] this patch broke multicast traffic send
    from ports with disabled port security. And that broke L3HA routers
    as keepalived processes couldn't talk to each other.
    During attempt to fix that issue with keepalived we found out another
    corner cases which we may break and in fact to fix them, we would
    effectively revert this change and allow multicast traffic for all
    ports in e.g. networks with ports which have port security and ports
    which don't have port security and are on same node.
    As we also don't really know what other corner cases we may hit going
    further with that, lets revert this patch.
    As a follow up patch I will propose new patch which will document
    differences in handling multicast traffic between iptables and
    openvswitch based firewall drivers.
    
    [1] https://bugs.launchpad.net/neutron/+bug/1899967
    
    Change-Id: I37a8b33cf8e16d5bb5dc1966fc2dca6bb619026c
    Closes-Bug: #1899967


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

Title:
  L3HA Router in primary state on all nodes

Status in neutron:
  Fix Released

Bug description:
  It seems that after we merged patch
  https://review.opendev.org/#/c/748719/ we broke communication between
  keepalived processes on ha network and because of that HA routers are
  always master on all nodes.

  We found that in tobiko job:
  https://c5e3229f1913e164c6b4-b80014e5a7a6453c822c4dc8f22159da.ssl.cf2.rackcdn.com/758033/2/check
  /devstack-tobiko-faults-
  centos/fb012bd/test_results_01_create_resources_scenario.html

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


References