Reviewed: https://review.openstack.org/300571 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=70068992e37c80e9aa8e70f017aa35132d7e5aee Submitter: Jenkins Branch: master
commit 70068992e37c80e9aa8e70f017aa35132d7e5aee Author: Oleg Bondarev <[email protected]> Date: Fri Apr 1 19:40:20 2016 +0300 Use new DB context when checking if agent is online during rescheduling Commit 9ec466cd42de94c2fad091edfd7583a5f47eb87a was not enough since it checked l3 agents in the same transaction that was used to fetch down bindings - so agents always were down even if actually they went back online. This commit adds context creation on each iteration to make sure we use new transaction and fetch up-to-date info for the agent. Closes-Bug: #1522436 Change-Id: I12a4e4f4e0c2042f0c0bf7eead42baca7b87a22b ** 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/1522436 Title: No need to autoreschedule routers if l3 agent is back online Status in neutron: Fix Released Bug description: - in case l3 agent goes offline the auto-rescheduling task is triggered and starts to reschedule each router from dead agent one by one - If there are a lot of routers scheduled to the agent, rescheduling all of them might take some time - during that time the agent might get back online - currently autorescheduling will be continued until all routers are rescheduled from the (already alive!) agent The proposal is to skip rescheduling if agent is back online. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1522436/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
