If you have 'allow_automatic_dhcp_failover' set to True then it will
automatically remove networks from DHCP agents that are offline.
However, this only applies to networks that are in the admin_state_up=True
condition. If you explicitly set them to admin_state_up=False then
automatic rescheduling won't occur. This was intentionally done so
operators could avoid having networks rescheduled from DHCP agents they
were performing short term maintenance on.
So next time just start by shutting the agent down and ensuring that
'allow_automatic_dhcp_failover' is set to True in your server config and it
On Sun, Aug 6, 2017 at 3:16 PM, Xav Paice <xavpa...@gmail.com> wrote:
> Yeah, it's an odd one for sure, in my experience at least they do need to
> be manually re-scheduled.
> On Sun, 6 Aug 2017 at 11:27 Curtis <serverasc...@gmail.com> wrote:
>> I'm in the process of testing out moving around some neutron services.
>> I'm starting with dhcp-agent. I've got neutron set to have 3 dhcp
>> instances per network.
>> I set the admin state of a single dhcp agent to down, then all the
>> dhcp namespaces were automatically removed from the node running dhcp
>> agent. Then I deleted the agent thinking the dhcp services would get
>> rescheduled to another node, but they were not. So now I've just got
>> two dhcp servers for most networks.
>> Am I, as admin, expected to now do something like add all the networks
>> with only 2 dhcp servers to a new dhcp-agent (using neutron
>> dhcp-agent-network-add) or should neutron reschedule them
>> I'm hoping I just missed a step here. :)
>> OpenStack-operators mailing list
> OpenStack-operators mailing list
OpenStack-operators mailing list