Sławek Kapłoński 39b9197f6f Don't set administratively disabled ports as ACTIVE ... There was a race condition during port update to disable it. In case when neutron-server receives port update call to set admin_state_down on port, it sends PORT_UPDATE notification to agents. Then both L2 and DHCP agents start doing their job with port. L2 agent asks neutron-server about device details and during processing this call server sets port's status to DOWN if its admin_state_up = False. Problem is that sometimes just after that, DHCP agent will send to neutron server notification that provisioning for this port is finished. As there is no any other provisioning block in db (because it is just port update) neutron-server is setting port's status to ACTIVE. This patch fixes this issue by allowing to transition to ACTIVE only ports which are administratively enabled. Change-Id: If506e0ff68fc49748f19618470c85901339a419b Closes-Bug: #1757089 (cherry picked from commit 2a1319ab7a)		2018-06-21 07:40:49 +00:00
..
common	Utils: make delete_port_on_error more informative	2017-06-03 15:07:21 +00:00
ml2	Don't set administratively disabled ports as ACTIVE	2018-06-21 07:40:49 +00:00
__init__.py	Finish off rebranding of the Nicira NVP plugin	2014-03-01 18:14:52 -08:00