LBaaS v2 healthmonitor wrong status detection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Expired
|
High
|
Unassigned |
Bug Description
Summary:
After enabling health monitor loadbalancer on any request returns
HTTP/1.0 503 Service Unavailable
I have loadbalancer with vip ip 10.123.21.15. HTTP listener, pool and member with IP 10.123.21.12.
I check status of web-server by:
curl -I -X GET http://
...
HTTP/1.1 200 OK
But when I add healthmonitor:
neutron lbaas-healthmon
--delay 5 \
--max-retries 2 \
--timeout 10 \
--type HTTP \
--url-path /owncloud/
--pool owncloud-
neutron lbaas-healthmon
+------
| Field | Value |
+------
| admin_state_up | True |
| delay | 5 |
| expected_codes | 200 |
| http_method | GET |
| id | cf3cc795-
| max_retries | 2 |
| name | |
| pools | {"id": "edcd43a2-
| tenant_id | b5d8bbe7742540c
| timeout | 10 |
| type | HTTP |
| url_path | /owncloud/
+------
I expect:
curl -I -X GET http://
...
HTTP/1.1 200 OK
But result:
curl -I -X GET http://
...
HTTP/1.0 503 Service Unavailable
Direct request to member:
curl -I -X GET http://
...
HTTP/1.1 200 OK
In neutron logs have no ERROR.
Some detail about configuration:
I have 3 controllers. Installed by Fuel with l3 population and DVR enabled.
lbaas_agent.ini
interface_
neutron lbaas-loadbalan
{
"loadbalancer": {
"name": "owncloud-app-lb",
{
],
}
],
"pools": [
{
},
],
}
],
"id": "67a9602e-
}
tags: | added: lbaas |
affects: | neutron → octavia |
tags: | removed: lbaas |
Changed in octavia: | |
status: | New → Incomplete |
Hi Sergey,
What LBaaS driver and OpenStack release are you using?