yahoo-eng-team team mailing list archive

[OpenStack Infra <1461148@xxxxxxxxxxxxxxxxxx>]

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

commit fc514b8e71d6ba7a1541ff925c63becf8834f6f5
Author: Ann Kamyshnikova <akamyshnikova@xxxxxxxxxxxx>
Date:   Wed Nov 18 17:03:12 2015 +0300

    Update HA router state if agent is not active
    
    If L3 agent is marked dead it is still show as 'active' in the HA
    router states on that agent. Current change adds check for such
    case and updates HA router state from 'active' to 'standby' if
    agent is dead.
    
    Closes-bug: #1461148
    
    Change-Id: Ie02e787a5b30cbe01694081cdec924304ab2ef41


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

Title:
  Dead L3 agent should reflect HA router states

Status in neutron:
  Fix Released

Bug description:
  The main use case of L3 HA is bouncing back from a machine (That is
  running a L3 agent) dying. In this case, with bp/report-ha-router-
  master merged, any active routers on that node will remain active in
  the Neutron DB (As the dead agent cannot update the server of
  anything). A backup node will pick up the routers previously active on
  the dead node and will update their status, resulting in the Neutron
  DB having the router 'active' on two different nodes. This can mess up
  l2pop as HA router interfaces will now be arbitrarily hosted on any of
  the 'active' hosts.

  The solution would be that when a L3 agent is marked as dead, to go
  ahead and change the HA router states on that agent to from active to
  standby, and also to update the router ports 'host' value to point to
  the new active agent.

  Note: This bug is at least partially coupled with
  https://bugs.launchpad.net/neutron/+bug/1365476. Ideally we could
  solve the two bugs in two separate patches with no dependencies.

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