octavia

Deleting member does not remove amphora from network/subnet

Bug #1609050 reported by Brandon Logan on 2016-08-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
​ octavia
In Progress
Undecided
li,chen
Also affects project (?) Also affects distribution/package Nominate for series

Bug Description

Steps to reproduce:

1. Create loadbalancer, listener, and pool
2. Create member providing a subnet of a network that is not the vip network
3. View the amphora(e) network interfaces via nova interface-list. You should see the new member network and IP.
4. Delete the member from the pool.
5. View the amphora(e) network interfaces via nova interface-list. You will see that the interface still exists on the amphora even though it shouldn't.

Also, looking on the amphora itself, it seems the interface files remain for that interface as well (/etc/netns/amphora-haproxy/network/interfaces.d/ethX.cfg). Might be related, may be a different bug.

See original description
Brandon Logan (brandon-logan) on 2016-08-02
description: updated
li,chen (chen-li) wrote :

https://review.openstack.org/#/c/347121/

Changed in octavia:
assignee: nobody → li,chen (chen-li)
OpenStack Infra (hudson-openstack) on 2016-08-09
Changed in octavia:
status: New → In Progress
OpenStack Infra (hudson-openstack) wrote : Change abandoned on octavia (master)

Change abandoned by li,chen (<email address hidden>) on branch: master
Review: https://review.openstack.org/347121

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.
Subscribing...

Other bug subscribers