[Bug 1664203] Re: v1 driver does not delete namespace when pool deleted
Louis Bouchard
louis.bouchard at canonical.com
Fri Feb 24 14:25:48 UTC 2017
** Also affects: neutron-lbaas (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: neutron-lbaas (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: neutron-lbaas (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: neutron-lbaas (Ubuntu Yakkety)
Status: New => Won't Fix
** Changed in: neutron-lbaas (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1664203
Title:
[SRU] v1 driver does not delete namespace when pool deleted
Status in Ubuntu Cloud Archive:
New
Status in neutron-lbaas package in Ubuntu:
In Progress
Status in neutron-lbaas source package in Trusty:
New
Status in neutron-lbaas source package in Xenial:
In Progress
Status in neutron-lbaas source package in Yakkety:
Won't Fix
Bug description:
[Impact]
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.
[Test Case]
Please see http://pastebin.ubuntu.com/24058957/
[Regression Potential]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1664203/+subscriptions
More information about the Ubuntu-sponsors
mailing list