Clean out namespaces even if we don't delete namespaces
Even when we don't enable namespace deletion, we still want to run the
code that cleans out the namespaces so that the devices get unplugged,
etc. Otherwise, routers deleted while the agent is down will continue
to operate as if they were never deleted.
The trade-off to consider here is that if there are many stale
namespaces this will slow down the restart of the L3 agent. The best
option is to get namespace deletion working correctly. However, where
that has not been worked out yet, this patch provides the cleaning
service for deleted routers.
Reviewed: https:/ /review. openstack. org/84570 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=8ab6fd6d7e5 21a3692f57542e5 c5c5d513d57ccc
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8ab6fd6d7e521a3 692f57542e5c5c5 d513d57ccc
Author: Carl Baldwin <email address hidden>
Date: Tue Apr 1 22:16:59 2014 +0000
Clean out namespaces even if we don't delete namespaces
Even when we don't enable namespace deletion, we still want to run the
code that cleans out the namespaces so that the devices get unplugged,
etc. Otherwise, routers deleted while the agent is down will continue
to operate as if they were never deleted.
The trade-off to consider here is that if there are many stale
namespaces this will slow down the restart of the L3 agent. The best
option is to get namespace deletion working correctly. However, where
that has not been worked out yet, this patch provides the cleaning
service for deleted routers.
Change-Id: Ic7b4608a23c4d9 530f521d5faff3f 8526200b92e
Closes-Bug: #1301042
Related-Bug: #1052535