octavia

Members go into ERROR operating status upon adding Health Monitor

Bug #1555854 reported by Franklin Naval
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
octavia
Expired
High
Unassigned

Bug Description

1. Create a LB with 2 members.
2. Do a list members and observe that the status is "NO_MONITOR"
3. Configure a health monitor for the pool.
4. Do a list members.

Result: The members show up as operating status "ERROR"
Expected: The members should show up as operating status "ONLINE"

see: https://github.com/openstack/octavia/blob/master/octavia/controller/healthmanager/update_db.py#L168

related to: 1547609

Tags: osic
Michael Johnson (johnsom)
Changed in octavia:
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Michael Johnson (johnsom) wrote :

I cannot reproduce this. I setup a load balancer as described in this bug. I used mysql to see the status (neutron-lbaas is not syncing the status currently it appears).

When I created the LB all members were in the "NO_MONITOR" state as expected.

I then added the following health monitor:
neutron lbaas-healthmonitor-create --name hm1 --expected-codes 200 --http-method GET --delay 1 --max-retries 1 --timeout 5 --type HTTP --pool pool1

Watching the mysql member table I saw the members go straight from "NO_MONITOR" to "ONLINE"

Can you re-test and provide more information?

Revision history for this message
Adam Harwell (adam-harwell) wrote :

Can anyone verify whether this bug still exists?

tags: added: osic
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for octavia because there has been no activity for 60 days.]

Changed in octavia:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.