Port binding is not getting updated on DHCP rescheduling
Bug #1522334 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Invalid
|
High
|
MOS Neutron | ||
6.1.x |
Fix Released
|
High
|
MOS Neutron | ||
7.0.x |
Fix Released
|
High
|
MOS Neutron | ||
8.0.x |
Invalid
|
High
|
MOS Neutron |
Bug Description
Tunnels are not getting built properly when DHCP port is rescheduled because port binding is not getting update.
Also, it can affect thrid-party plugins that would not wire new DHCP port properly without correct host.
Upstream bug: https:/
Reviewed: https:/ /review. fuel-infra. org/12351 ci/fuel- 6.1/2014. 2
Submitter: Vitaly Sedelnik <email address hidden>
Branch: openstack-
Commit: ec1526900a1f728 5dfc3f1e56b0105 a790c86484
Author: venkata anil <email address hidden>
Date: Thu Dec 3 09:34:49 2015
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).
Cherry-picked from: 571453c614577ff d47e23de9a35863 d2f2119583 95af116ccd31a43 853332ae317
Change-Id: Ib7d7dcddee0053
Closes-bug: #1522334