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

Ubuntu Foundations Team Bug Bot 1664203 at bugs.launchpad.net
Mon Feb 13 20:29:05 UTC 2017

The attachment "lp1664203-xenial-mitaka.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron-lbaas in Ubuntu.

  v1 driver does not delete namespace when pool deleted

Status in Ubuntu Cloud Archive:
Status in neutron-lbaas package in Ubuntu:
  In Progress

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:

More information about the Ubuntu-openstack-bugs mailing list