yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1884906@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

-- 
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:
  New

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