Deleting member does not remove amphora from network/subnet
Bug #1609050 reported by
Brandon Logan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| octavia |
Invalid
|
Undecided
|
Unassigned | ||
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/
| description: | updated |
Revision history for this message
| li,chen (chen-li) wrote | #1 |
| Changed in octavia: | |
| assignee: | nobody → li,chen (chen-li) |
| Changed in octavia: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on octavia (master) | #2 |
Revision history for this message
| Gregory Thiemonge (gthiemonge) wrote auto-abandon-script | #3 |
| Changed in octavia: | |
| assignee: | li,chen (chen-li) → nobody |
| status: | In Progress → Invalid |
| tags: | added: auto-abandon |
To post a comment you must log in.
https:/