Public bug reported: Neutron Liberty, Ubuntu 14.04
3 controllers(3 l3-agents are available and active.), 1 compute I have max_l3_agents_per_router=2, router is scheduled to 2 agents. If you of one these agents is stopped I will have something like: root@node-1:~# neutron l3-agent-list-hosting-router r3 +--------------------------------------+-------------------+----------------+-------+----------+ | id | host | admin_state_up | alive | ha_state | +--------------------------------------+-------------------+----------------+-------+----------+ | 1fa93569-fc36-4fb4-b467-85b11ba5f20c | node-3.domain.tld | True | xxx | active | | 709998f7-cc64-4b6a-9777-6c815dfebb5c | node-2.domain.tld | True | :-) | active | +--------------------------------------+-------------------+----------------+-------+----------+ The point is: router won't be rescheduled from dead agent and scheduled for another available active one. This situation can be avoided by simply setting max_l3_agents_per_router=0, but for current case is it possible to have a solution? ** Affects: neutron Importance: Undecided Assignee: Ann Kamyshnikova (akamyshnikova) Status: New ** Tags: l3-ha -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1511732 Title: HA router schedule for another active agent Status in neutron: New Bug description: Neutron Liberty, Ubuntu 14.04 3 controllers(3 l3-agents are available and active.), 1 compute I have max_l3_agents_per_router=2, router is scheduled to 2 agents. If you of one these agents is stopped I will have something like: root@node-1:~# neutron l3-agent-list-hosting-router r3 +--------------------------------------+-------------------+----------------+-------+----------+ | id | host | admin_state_up | alive | ha_state | +--------------------------------------+-------------------+----------------+-------+----------+ | 1fa93569-fc36-4fb4-b467-85b11ba5f20c | node-3.domain.tld | True | xxx | active | | 709998f7-cc64-4b6a-9777-6c815dfebb5c | node-2.domain.tld | True | :-) | active | +--------------------------------------+-------------------+----------------+-------+----------+ The point is: router won't be rescheduled from dead agent and scheduled for another available active one. This situation can be avoided by simply setting max_l3_agents_per_router=0, but for current case is it possible to have a solution? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1511732/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp