Delete fipnamespace when external net removed on DVR
The fipnamespace is associated with an external network
on a given node. In the case of DVR there is just one
single FIP namespace for a given node.
We have seen some race conditions in the agent for creation
and deletion of the fip namespace. See the bug report for
details on the failure.
So in order to address this race condition and make the
code more stable, we will be cleaning up the fip namespace
only when an external network is removed.
The server will be sending a rpc notification message to
the agent to cleanup the fip namespace when the external
net is removed.
This patch address the above mentioned issue by not constantly
deleting and creating the fip namespace.
Reviewed: https:/ /review. openstack. org/273236 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=05de3183a3a 85a08d8ea4cfcd8 7cefa8b67ceb4b
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit 05de3183a3a85a0 8d8ea4cfcd87cef a8b67ceb4b
Author: Swaminathan Vasudevan <email address hidden>
Date: Thu Oct 1 11:48:55 2015 -0700
Delete fipnamespace when external net removed on DVR
The fipnamespace is associated with an external network
on a given node. In the case of DVR there is just one
single FIP namespace for a given node.
We have seen some race conditions in the agent for creation
and deletion of the fip namespace. See the bug report for
details on the failure.
So in order to address this race condition and make the
code more stable, we will be cleaning up the fip namespace
only when an external network is removed.
The server will be sending a rpc notification message to
the agent to cleanup the fip namespace when the external
net is removed.
This patch address the above mentioned issue by not constantly
deleting and creating the fip namespace.
Conflicts: tests/functiona l/agent/ test_l3_ agent.py
neutron/
Closes-Bug: #1501873 109204dc16259c0 e4ce1c903a) ad7db09942578b1 a456a9bd418
(cherry picked from commit cb465d40f59bfbc
Change-Id: I86869f66d4afff