yahoo-eng-team team mailing list archive

[OpenStack Infra <1597461@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/357458
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=25f5912cf8f69f18d111bd60a6cc6ee488755ff3
Submitter: Jenkins
Branch:    master

commit 25f5912cf8f69f18d111bd60a6cc6ee488755ff3
Author: AKamyshnikova <akamyshnikova@xxxxxxxxxxxx>
Date:   Thu Aug 18 23:18:40 2016 +0300

    Check for ha port to become ACTIVE
    
    After reboot(restart of l3 and l2 agents) of the node routers
    can be processed by l3 agent before openvswitch agent sets up
    appropriate ha ports. This change add notification for l3 agent
    that ha port becomes ACTIVE and keepalived can be enabled.
    
    Closes-bug: #1597461
    
    Co-Authored-By: venkata anil <anilvenkata@xxxxxxxxxx>
    
    Change-Id: Iedad1ccae45005efaaa74d5571df04197757d07a


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

Title:
  L3 HA: 2 masters after reboot of controller

Status in neutron:
  Fix Released

Bug description:
  ENV: Mitaka 3 controllers 45 computes DVR + L3 HA (L3 HA as well
  affected)

  After reboot of controller on which l3 agent is active, another l3
  agent becomes active. When rebooted node recover, that l3 agent
  becomes active as well - this lead to extra loss of external
  connectivity in tenant network. After some time the only one agent
  remains to be active - the one from rebooted node. Sometimes
  connectivity does not come back, as snat port ends up on wrong host.

  The root cause of this problem is that routers are processed by l3
  agent before openvswitch agent sets up appropriate ha ports, so for
  some time recovered ha routers is isolated from ha routers on other
  hosts and becomes active.

  The possible solution for this is proper serialization of ha network
  creation by l3 agent after ha network is set up on controller.

  With 100 routers and networks this issues has been reproduced with
  every reboot.

  Actually this is L3 HA problem, it is just increased with DVR as the
  number of ports that openvswith agent should handle is higher.

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