with the health monitor configured "lb-member-list" doesnt get updated when one of the member in the pool goes down
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Won't Fix
|
High
|
Rudra Rugge | |||
R2.0 |
Won't Fix
|
High
|
Rudra Rugge | |||
R2.1 |
Won't Fix
|
High
|
Rudra Rugge | |||
R3.0 |
Fix Committed
|
High
|
Rudra Rugge | |||
R3.1 |
Fix Committed
|
High
|
Rudra Rugge | |||
Trunk |
Fix Committed
|
High
|
Rudra Rugge |
Bug Description
R1.10 Build 12
Configured 3 back-end servers in the pool. Configured the health monitor and associated it with the pool.
Even when one of the member in the pool goes down "lb-member-list" still shows 3 members as ACTIVE.
root@a5s311:~# neutron lb-healthmonito
+------
| id | type | admin_state_up |
+------
| d3bdf009-
+------
root@a5s311:~# neutron lb-pool-show mypool
+------
| Field | Value |
+------
| admin_state_up | True |
| description | |
| health_monitors | d3bdf009-
| id | c49931cd-
| lb_method | ROUND_ROBIN |
| members | 6d8d6c16-
| | b1328d83-
| | 2a1d7542-
| name | mypool |
| protocol | HTTP |
| provider | opencontrail |
| status | ACTIVE |
| subnet_id | 6a3bea8e-
| tenant_id | 250ea904-
| vip_id | 1744c174-
+------
root@a5s311:~# nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 7562a11f-
| 1cfc4333-
| 22971dfb-
| ffe244bc-
+------
root@a5s311:~# neutron lb-member-list
+------
| id | address | protocol_port | admin_state_up | status |
+------
| 2a1d7542-
| 6d8d6c16-
| b1328d83-
+------
and are we suppose to see the pool info in the below cli after we associate the health monitor with the pool?
root@a5s311:~# neutron lb-healthmonito
+------
| Field | Value |
+------
| admin_state_up | True |
| delay | 3 |
| expected_codes | 200 |
| http_method | GET |
| id | d3bdf009-
| max_retries | 3 |
| status | ACTIVE |
| tenant_id | 250ea904-
| timeout | 3 |
| type | HTTP |
| url_path | / |
+------
bug update...