yahoo-eng-team team mailing list archive

[OpenStack Infra <1481588@xxxxxxxxxxxxxxxxxx>]

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

commit 938937b94415bb79accb026a7bcc2d2a9d1dcf13
Author: Ann Kamyshnikova <akamyshnikova@xxxxxxxxxxxx>
Date:   Wed Aug 24 20:52:47 2016 +0300

    Set L3 agent standby if admin_state_up=False
    
    If admin_state_up set to False L3 agent still shows 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's admin_state_up is False.
    
    Change-Id: Iaa800221fcfcd41e81ade5136a2a513a2cce8d5b
    Closes-bug: #1481588


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

Title:
  Wrong HA router state after setting the admin_state_up to False

Status in neutron:
  Fix Released

Bug description:
  In an L3 HA Setup with multiple network nodes, we can query the agent
  hosting the Master HA router via l3-agent-list-hosting-router.

  For example
  neutron l3-agent-list-hosting-router h1
  +--------------------------------------+----------------+----------------+-------+----------+
  | id                                   | host           | admin_state_up | alive | ha_state |
  +--------------------------------------+----------------+----------------+-------+----------+
  | 05cbe1b6-5b1e-4685-9a67-e55741b2b4b6 | networknode_1  | True           | :-)   | active   |
  | 40cfc10c-ae96-4715-9aa9-d5af668a4c1e | networknode_2  | True           | :-)   | standby  |
  | 14b81831-366e-43af-8be4-50f7939981fe | networknode_3  | True           | :-)   | standby  |
  +--------------------------------------+----------------+----------------+-------+----------+

  Now if we set the admin state of networknode_1 to down (i.e., neutron
  agent-update <agent-id> --admin_state_up=False), HA router would be
  deleted from the agent and one of the backup HA Routers would take
  over the role of Master.

  In such a situation, when we query the active HA router info, the
  state of the router on the agent is still shown as 'active' and is not
  updated, which could really be confusing.

  neutron l3-agent-list-hosting-router h1
  +--------------------------------------+----------------+----------------+-------+----------+
  | id                                   | host           | admin_state_up | alive | ha_state |
  +--------------------------------------+----------------+----------------+-------+----------+
  | 05cbe1b6-5b1e-4685-9a67-e55741b2b4b6 | networknode_1  | False          | :-)   | active   |
  | 40cfc10c-ae96-4715-9aa9-d5af668a4c1e | networknode_2  | True           | :-)   | active   |
  | 14b81831-366e-43af-8be4-50f7939981fe | networknode_3  | True           | :-)   | standby  |
  +--------------------------------------+----------------+----------------+-------+----------+

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