When using LBaaS and trying to delete a subnet, neutron has no way of
knowing if the subnet is associated to some pool. As a result, the
subnet is deleted but the pool remains associated to the (now
nonexistent) subnet_id. This patch adds a check in LBaaS side to
prevent such a case, using the callbacks system.
Reviewed: https:/ /review. openstack. org/174384 /git.openstack. org/cgit/ openstack/ neutron- lbaas/commit/ ?id=a3a35ff36f6 0b5bfb04f3bb165 23b9031e9ded2f
Committed: https:/
Submitter: Jenkins
Branch: master
commit a3a35ff36f60b5b fb04f3bb16523b9 031e9ded2f
Author: John Schwarz <email address hidden>
Date: Thu Apr 16 14:08:07 2015 +0300
Prevent deletion of a subnet with lbaas v1 pool
When using LBaaS and trying to delete a subnet, neutron has no way of
knowing if the subnet is associated to some pool. As a result, the
subnet is deleted but the pool remains associated to the (now
nonexistent) subnet_id. This patch adds a check in LBaaS side to
prevent such a case, using the callbacks system.
Closes-Bug: #1413817 3df792fdabcf540 163007a3f33 fd919c92d65b57d a56c63e053c
Change-Id: I1a8893453b0b62
Depends-on: I3d5e231b67c72f