dhcp agent binding count greather than dhcp_agents_per_network

[yaoguang]

neutron version: train
dhcp_agents_per_network = 2
execute command "neutron dhcp-agent-network-add" bind a network to dhcp agent, but not check configuration dhcp_agents_per_network.

[Bence Romsics (bence-romsics)]

Hi,

Thank you for your report!

I'm not sure if this is properly documented, but my understanding was that dhcp_agents_per_network is used only when autoscheduling dhcp agents. When we manually schedule agents then the config option is purposefully ignored, not to interfere with the manual operations. Like if we add a third, would you expect one of the three to be magically removed? Which one? Can neutron always choose the proper one to unschedule? Or should neutron prohibit the unscheduling of an agent when we go under two? Would you consider the manual operation still usable if neutron did those things?

I believe that manual schedule/unschedule operations purposefully allow temporary violations of dhcp_agents_per_network and that it's the admin's responsibility to leave the system in a known good state after such operations.

What do you think?

[yaoguang (yaoguang100)]

Ok, i think it makes sense.

[yaoguang (yaoguang100)]

I still have some questions. If the index is no longer 1 or 2 after manual scheduling, automatic scheduling is also affected, although the number of bindings is still 2.