Reviewed: https://review.opendev.org/737736 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2bb514f2d73a64b6f954990a2ff12f5baa3a97cd Submitter: Zuul Branch: master
commit 2bb514f2d73a64b6f954990a2ff12f5baa3a97cd Author: Rodolfo Alonso Hernandez <[email protected]> Date: Wed Jun 24 09:58:09 2020 +0000 L3 agent scheduler should return a valid index if manual scheduling When retrieving a vacant L3 agent binding index, if "is_manual_scheduling" is set, the method "get_vacant_binding_index" should always return a valid binding index. If the existing binding indexes are sequentially aligned, the method will return a new one on top; if there is a gap in the binding indexes list, the first free index will be returned. Closes-Bug: #1884906 Change-Id: I0a89bca0734d3e735fb357e488f85589e81d709f ** 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/1884906 Title: L3 agent cannot be manually scheduled Status in neutron: Fix Released Bug description: This bug is similar to https://bugs.launchpad.net/neutron/+bug/1883513. When a new L3 agent is manually scheduled, "L3AgentSchedulerDbMixin.get_vacant_binding_index" should always provide a vacant index, even if this index exceeds the maximum number of configured L3 agents. That means, when "is_manual_scheduling=True", a valid vacant index number should be provided. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1884906/+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
