When a dhcp server is moved to new host on failover,
tunnel is not created.
When a dhcp server is moved to new host,
1) network-hostagent binding is updated(properly i.e with new host).
2) dhcp port-hostagent binding is not updated
( dhcp port is still bound to old host)
If dhcp port-bound agent is different from the new dhcp agent
(which is now taking care of this dhcp port), neutron plugin won't
notify the l2pop, and hence tunnel is not created.
As after failover, the new agent is taking care of this dhcp port,
update portbinding with the new host. This will allow neutron plugin
to notify l2pop(which will create tunnel).
Reviewed: https:/ /review. openstack. org/197937 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=571453c6145 77ffd47e23de9a3 5863d2f2119583
Committed: https:/
Submitter: Jenkins
Branch: master
commit 571453c614577ff d47e23de9a35863 d2f2119583
Author: venkata anil <email address hidden>
Date: Thu Jul 2 11:22:39 2015 +0000
Update dhcp host portbinding on failover
When a dhcp server is moved to new host on failover,
tunnel is not created.
When a dhcp server is moved to new host,
1) network-hostagent binding is updated(properly i.e with new host).
2) dhcp port-hostagent binding is not updated
( dhcp port is still bound to old host)
If dhcp port-bound agent is different from the new dhcp agent
(which is now taking care of this dhcp port), neutron plugin won't
notify the l2pop, and hence tunnel is not created.
As after failover, the new agent is taking care of this dhcp port,
update portbinding with the new host. This will allow neutron plugin
to notify l2pop(which will create tunnel).
Change-Id: Ib7d7dcddee0053 95af116ccd31a43 853332ae317
Closes-bug: #1411163