neutron/neutron/api
Kailun Qin b9f9c021c9 Block port update from unbound DHCP agent
Current DHCP port management in Neutron makes the server to clear the
device_id while the agent is responsible for setting it.

This may cause a potential race condition, for example during network
rescheduling. The server aims to clear the device_id on a DHCP port and
assign the network to another agent while the old agent might just be
taking possession of the port. If the DHCP agent takes possession of the
port (i.e., update port...set the device_id) before the server clears
it, then there is no issue. However, if this happens after the clear
operation by server then the DHCP port would be updated/marked to be
owned by the old agent.

When the new agent takes over the network scheduled to it, it won't be
able to find a port to reuse so that an extra port might need to be
created. This leads to two issues:
1) an extra port is created and never deleted;
2) the extra port creation may fail if there are no available IP
addresses.

This patch proposes a validation check to prevent an agent from updating
a DHCP port unless the network is bound to that agent.

Co-authored-by: Allain Legacy <Allain.legacy@windriver.com>

Closes-Bug: #1795126
Story: 2003919
Change-Id: Ie619516c07fb3dc9d025f64c0e1e59d5d808cb6f
(cherry picked from commit b70ee4df88)
2018-12-18 19:58:32 +08:00
..
rpc Block port update from unbound DHCP agent 2018-12-18 19:58:32 +08:00
v2 use callback payloads for REQUEST/RESPONSE events 2017-12-24 07:27:11 +00:00
views Add a new configuration variable for api links. 2017-04-18 15:16:41 +00:00
__init__.py Added API extensions to detect sorting/pagination features 2016-08-01 22:57:15 +02:00
api_common.py Make code follow log translation guideline 2017-08-14 02:01:48 +00:00
extensions.py Support that an extension extends a sub-resource 2017-11-15 08:59:45 +01:00
versions.py Remove dead versions code 2017-09-19 14:54:33 -07:00