Description of problem: Orphaned namespaces remain after Neutron LBaaS stack deleted Version-Release number of selected component (if applicable): Red Hat OpenStack Platform 10 How reproducible: Always Steps to Reproduce: (1) Create a Neutron LBaaS stack on RHOS 10 - neutron lbaas-loadbalancer-create subnet-one --name lbtest01 - neutron lbaas-listener-create --loadbalancer lbtest01 --protocol-port 80 --protocol HTTP --name testlistener01 - neutron lbaas-pool-create --name testpool01 --protocol HTTP --listener testlistener01 --lb-algorithm ROUND_ROBIN - neutron lbaas-member-create testpool01 --address 192.168.1.2 --protocol-port 80 --subnet subnet-one - neutron lbaas-member-create testpool01 --address 192.168.1.3 --protocol-port 80 --subnet subnet-one - neutron lbaas-healthmonitor-create --delay 3 --type HTTP --max-retries 3 --timeout 3 --pool testpool01 (2) Note the qlbaas namespace on the controller - ip netns | grep qlbaas (3) Delete the LBaaS stack - neutron lbaas-healthmonitor-delete <UUID> - neutron lbaas-pool-delete <UUID< - neutron lbaas-listener-delete <UUID> - neutron lbaas-loadbalancer-delete <UUID> (4) List the namespaces on the controller and observe the qlbaas namespace still exists - ip netns | grep qlbaas Actual results: Namespaces are still visible Expected results: Namespaces should be removed when loadbalancer is deleted Additional info: https://review.openstack.org/#/c/426209/ https://bugs.launchpad.net/octavia/+bug/1495430
Hot fix approved for Australian Signals Directorate. As per comment 1, the fix was already merged in OSP 10, and will be available in the next z-stream release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1594