Ubuntu Cloud Archive

  1. Series newton
  2. Bug #1495430
  3. Comment #2

Comment 2 for bug 1495430

Revision history for this message
P Ingle (pingle) wrote :

On Kilo release with LBaaS v2, it was observed that the lbaas namespace does not get deleted even after loadbalancer object is deleted.

:~# neutron lbaas-loadbalancer-list
+--------------------------------------+------+-------------+---------------------+----------+
| id | name | vip_address | provisioning_status | provider |
 +--------------------------------------+------+-------------+---------------------+----------+
| f5b74cd4-df4c-48f9-a004-98190d2cc091 | lb1 | 8.8.8.6 | ACTIVE | haproxy |
 +--------------------------------------+------+-------------+---------------------+----------+
:~# ip netns | grep f5b74cd4-df4c-48f9-a004-98190d2c
qlbaas-f5b74cd4-df4c-48f9-a004-98190d2cc091
:~# neutron lbaas-listener-delete listener1
Deleted listener: listener1
:~# ip netns | grep f5b74cd4-df4c-48f9-a004-98190d2c
qlbaas-f5b74cd4-df4c-48f9-a004-98190d2cc091
:~# neutron lbaas-loadbalancer-delete lb1
Deleted loadbalancer: lb1
:~# ip netns | grep f5b74cd4-df4c-48f9-a004-98190d2c
qlbaas-f5b74cd4-df4c-48f9-a004-98190d2cc091