[RFE] admin-state-down doesn't evacuate bindings in the dhcp_agent_id column
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Hi,
This is a real report from the production front, with a deployment causing us a lot of head-scratch because of a somehow broken hardware.
If, for some reason, a node running the neutron-dhcp-agent has some hardware issue, then an admin will probably want to disable the agent there. This is done with, for example:
neutron agent-update --admin-state-down e865d619-
or something like this too:
openstack network agent set --disable e865d619-
This works, and no new network will be assigned to this agent in the future, however, if there was some networks already assigned to this agent, they wont be evacuated.
What needs to be done is:
1/ Perform an update of the networkdhcpagen
2/ Restart the neutron-dhcp-agent process where the network have been moved, so that new dnsmasq process start for this network.
3/ Attempt to get the disabled agent to restart as well, knowing that reaching it may fail (since it has been disabled, that's probably because it's broken somehow...).
Currently, one needs to do all of this by hand. I've done that, and restored connectivity to a working DHCP server, as our user expected. This is kind of painful and boring to do, plus that's not really what an openstack user is expecting.
In fact, if we could also provide something like this, it'd be super nice:
openstack network agent evacuate e865d619-
then we'd be using it during the "set --disable" process.
Cheers,
Thomas Goirand (zigo)
Changed in neutron: | |
milestone: | none → ussuri-1 |
Changed in neutron: | |
milestone: | ussuri-1 → none |
This looks like an enhancement. I tagged it as RFE