Delete of last member does not remove it from haproxy config
Bug #1514510 reported by
Michael Johnson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Fix Released
|
Critical
|
Eran Raichstein |
Bug Description
I had setup a active/standby load balancer with two members. I then deleted them by UUID one after the other.
No errors were reported via CLI, o-cw, or amphora-agent logs but the last member is still present in the haproxy configuration file on the amphora. Logs indicated that a new configuration was pushed out and the listener restart command was run.
neutron lbaas-member-list shows no members are on the pool.
It is un-clear if this is an active/standby related bug or if it affects standalone mode as well. Could be related to bug #1494956
Changed in octavia: | |
assignee: | nobody → Eran Raichstein (eranra) |
To post a comment you must log in.
RE-RUN BUG # 1514510
The bug is still reproducible on current Octavia version. I deleted two members from the pool and both are removed from Neutron member list but only first one is removed from configuration file
1. using latest octavia / devstack versions::
Octavia is on :: bb1dfd5cc6e1d03 029cd795e5
commit cd5a50adb3a1a42
Author: Michael Johnson <email address hidden>
Date: Fri Dec 18 20:06:23 2015 +0000
2. Added /etc/octavia/ octavia. conf loadbalancer_ topology = ACTIVE_STANDBY (to force active standby configuration)
3. Executed ./stack.sh
DONE
4. Executed script to create : members, load balancer, listener, pool, and attach members (script content is listed bellow)
./create_ octavia_ demo_environmen t.sh fast
5. Checked that the LB works (didn't check for this bug any fail-over scenario)
curl 20.0.0.13
DONE
6. Listed nova VM's:
nova list --all-tenants
+------ ------- ------- ------- ------- ----+-- ------- ------- ------- ------- ------- ------- --+---- ------- ------- ------- ------- --+---- ----+-- ------- ---+--- ------- ---+--- ------- ------- ------- ------- ------- ------- ------- ------- ------- + ------- ------- ------- ------- ----+-- ------- ------- ------- ------- ------- ------- --+---- ------- ------- ------- ------- --+---- ----+-- ------- ---+--- ------- ---+--- ------- ------- ------- ------- ------- ------- ------- ------- ------- + 91ae-4812- 8f86-65f42ad79f d9 | amphora- 9be90952- fa15-40bc- bab2-13d10b6583 fd | 6200e5d3539b46e 3b748b01d99fad6 89 | ACTIVE | - | Running | lb-mgmt- net=192. 168.0.5; production= 20.0.0. 14; private=10.0.0.9 | f541-4226- 954d-c9615d447a d3 | amphora- d2840264- 61ed-4bee- 9013-61b9acb040 11 | 6200e5d3539b46e 3b748b01d99fad6 89 | ACTIVE | - | Running | lb-mgmt- net=192. 168.0.4; production= 20.0.0. 15; private=10.0.0.10 | cfae-4bcc- a356-8df2b32f48 c6 | demonode1 | 17e1e45ab43e473 0b06789a0a1a2c6 42 | ACTIVE | - | Running | private=10.0.0.4 | e0fa-4f34- 8b02-9a8417fac9 72 | demonode2 | 17e1e45ab43e473 0b06789a0a1a2c6 42 | ACTIVE | - | Running | private=10.0.0.5 | a3a6-4d73- 810b-5cabfde8c8 3e | demonode3 | 17e1e45ab43e473 0b06789a0a1a2c6 42 | ACTIVE | - | Running | private=10.0.0.6 | 88c4-4318- 9fef-9194ad0663 9b | demonode4 | 17e1e45ab43e473 0b06789a0a1a2c6 42 | ACTIVE | - | Running | private=10.0.0.7 | 66ef-4871- 98f4-93490c79b7 bb | demonode5 | 17e1e45ab43e473 0b06789a0a1a2c6 42 | ACTIVE | - | Running | private=10.0.0.8 | d8d8-4c7b- 90b3-1c00adf399 f0 | stresser1 ...
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+------
| 03c8c314-
| fb96cd7a-
| 81564676-
| e11c871c-
| 54e8ed66-
| 7201e674-
| 15662291-
| 76180a42-