[Bug 1664203] [NEW] v1 driver does not delete namespace when pool deleted

[Edward Hope-Morley]

Public bug reported:

The v1 services.loadbalancer.drivers.haproxy.namespace_driver has a bug
in that it deletes the haproxy state directory for a pool when it's vip
is deleted. This means that when the pool itself is deleted, its
associated namespace is never deleted since the delete is predicated on
the state patch being extant.

The v1 driver is deprecated as of the Liberty release and was totally
removed from the codebase in the Newton release. However, Openstack Kilo
and Mitaka are still supported in Ubuntu, the former requiring the v1
driver and the latter still capable of using it so we while upstream
will not accept a patch we will still patch the neutron-lbaas-agent
Ubuntu package to fix this issue.

** Affects: cloud-archive
     Importance: Undecided
         Status: New

** Affects: neutron-lbaas (Ubuntu)
     Importance: High
     Assignee: Edward Hope-Morley (hopem)
         Status: New


** Tags: sts

** Changed in: neutron-lbaas (Ubuntu)
    Milestone: ubuntu-16.04.2 => None

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron-lbaas in Ubuntu.
https://bugs.launchpad.net/bugs/1664203

Title:
  v1 driver does not delete namespace when pool deleted

Status in Ubuntu Cloud Archive:
  New
Status in neutron-lbaas package in Ubuntu:
  New

Bug description:
  The v1 services.loadbalancer.drivers.haproxy.namespace_driver has a
  bug in that it deletes the haproxy state directory for a pool when
  it's vip is deleted. This means that when the pool itself is deleted,
  its associated namespace is never deleted since the delete is
  predicated on the state patch being extant.

  The v1 driver is deprecated as of the Liberty release and was totally
  removed from the codebase in the Newton release. However, Openstack
  Kilo and Mitaka are still supported in Ubuntu, the former requiring
  the v1 driver and the latter still capable of using it so we while
  upstream will not accept a patch we will still patch the neutron-
  lbaas-agent Ubuntu package to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1664203/+subscriptions