dhcp agent binding count greather than dhcp_agents_per_network
Bug #2028544 reported by
yaoguang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Unassigned |
Bug Description
neutron version: train
dhcp_agents_
execute command "neutron dhcp-agent-
Changed in neutron: | |
status: | New → Invalid |
To post a comment you must log in.
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?