Kailun Qin 6295207e22 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) (cherry picked from commit b9f9c021c9)		2019-02-05 15:24:55 +00:00
..
rpc	Block port update from unbound DHCP agent	2019-02-05 15:24:55 +00:00
v2	Use addCleanup instead of tearDown	2017-02-02 22:07:26 +01:00
__init__.py	Send DHCP notifications regardless of agent status	2013-12-19 07:08:19 +00:00
test_extensions.py	neutron-lib: use CORE from neutron lib constants	2016-12-26 00:56:42 -08:00