Same as for bug 1222541 : auto_schedule_routers() has 'host' parameter
and is supposed to 'Schedule non-hosted routers to L3 Agent running on
host'. So supporting a single l3 agent is by design.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1222539
Title:
l3_agent_scheduler.ChanceScheduler.auto_schedule_routers only support
single l3 agent
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
try:
l3_agent = query.one()
except (exc.MultipleResultsFound, exc.NoResultFound):
LOG.debug(_('No enabled L3 agent on host %s'),
host)
return False
this is not a correct way for auto_schedule, meanwhile the
ChanceScheduler.schedule() support l3 agent candidates
active_l3_agents = plugin.get_l3_agents(context, active=True)
if not active_l3_agents:
LOG.warn(_('No active L3 agents'))
return
candidates = plugin.get_l3_agent_candidates(sync_router,
active_l3_agents)
so i think the auto_schedule should support multiple l3 agents as
schedule() does
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1222539/+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
