yahoo-eng-team team mailing list archive

[Kevin Benton <1507492@xxxxxxxxxxxxxxxxxx>]

This is expected behavior. That config value is to influence the
automatic scheduling. It shouldn't interfere with manual scheduling by
an admin.

** Changed in: neutron
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1507492

Title:
  manually schedule dhcp-agent doesn't check dhcp_agents_per_network

Status in neutron:
  Won't Fix

Bug description:
  We can use dhcp-agent-network-add to manually schedule a net to dhcp-
  agents. And when we manually schedule dhcp-agent, neutron code should
  check configure dhcp_agents_per_network, to verify current manually
  scheduling could be support or not.

  Pre-conditions:
  2 active dhcp-agents, agent-A and agent-B;
  network net-1 is bound on agent-A, use "neutron dhcp-agent-list-hosting-net" can to verify this;
  set dhcp_agents_per_network = 1 in /etc/neutron/neutron.conf;

  steps:
  directly run "neutron dhcp-agent-network-add AGENT-B-ID NET-1-ID" without remove net-1 from agent-A first.

  expected:
  warning or error to tells that couldn't schedule net-1 onto agent-B, for numbers of agents hosting net-1 couldn't be larger than dhcp_agents_per_network value.

  actual result:
  running "neutron dhcp-agent-list-hosting-net NET-1-ID" will output that net-1 is hosted by agent-A and agent-B now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1507492/+subscriptions