[Openstack-operators] Neutron DHCP failover bug

Clayton O'Neill clayton at oneill.net
Wed Sep 30 11:48:29 UTC 2015

We've seen similar issues with three network nodes, 2 dhcp agents per and
automatic failover.  We were seeing spurious failovers on a regular basis
and we'd end up finding out about it because an instance would fail to get
a lease.  When we investigated, usually see the issue you describe.
Automatic failover is on by default in Kilo, so it makes this bug much
worse.  We ended up turning off automatic failover because of this issue.
There are other fixes for failover in Liberty that were never back ported
to Kilo.

On Tue, Sep 29, 2015 at 9:58 PM, Sam Morrison <sorrison at gmail.com> wrote:

> Hi All,
> We are running Kilo and have come across this bug
> https://bugs.launchpad.net/neutron/+bug/1410067
> Pretty easy to replicate, have 2 network nodes, shutdown 1 of them and
> DHCP etc. moves over to the new host fine. Except doing a port-show on the
> DHCP port shows it still on the old host and in state BUILD.
> Everything works but the DB is in the wrong state.
> Just wondering if anyone else sees this and if so if they know the
> associated fix in Liberty that addresses this.
> Cheers,
> Sam
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150930/2e8f5a0f/attachment.html>

More information about the OpenStack-operators mailing list