Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1269981

Summary: lbaas doesn't monitor state of haproxy process
Product: Red Hat OpenStack Reporter: Jon Thomas <jthomas>
Component: openstack-neutron-lbaasAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: high    
Version: 6.0 (Juno)CC: amedeo.salvati, amuller, apevec, bperkins, jthomas, lhh, nyechiel, pablo.iranzo, rhos-maint
Target Milestone: ---Keywords: Reopened, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-04 01:21:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1273812    

Description Jon Thomas 2015-10-08 17:12:33 UTC 
Testing lb functionalities and I saw that if I kill haproxy process, or fence corresponding controller node who started haproxy, this lb never will be restarted on other controller nodes or on the same controller node.

On lbaas-agent.log log, if I kill haproxy process I can see logs like this:

2015-09-22 16:42:32.885 20418 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Error while connecting to stats socket: [Errno 111] ECONNREFUSED
2015-09-22 16:42:42.887 20418 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Error while connecting to stats socket: [Errno 111] ECONNREFUSED
2015-09-22 16:42:52.887 20418 WARNING neutron.services.loadbalancer.drivers.haproxy.namespace_driver [-] Error while connecting to stats socket: [Errno 111] ECONNREFUSED

Also, all LB status remain up, even after killing haproxy:
# neutron lb-pool-list
+--------------------------------------+----------+----------+-------------+----------+----------------+--------+
| id                                   | name     | provider | lb_method   | protocol | admin_state_up | status |
+--------------------------------------+----------+----------+-------------+----------+----------------+--------+
| 2c7b6eaf-a43b-447c-b88f-7a27fb58ffc9 | lbpool01 | haproxy  | ROUND_ROBIN | HTTP     | True           | ACTIVE |
+--------------------------------------+----------+----------+-------------+----------+----------------+--------+
Comment 2 Assaf Muller 2015-10-08 17:14:07 UTC 
Please re-open upstream, there's nothing RDO or OSP specific about this bug.
Comment 3 Assaf Muller 2015-10-08 17:14:58 UTC 
Apologies, I didn't know this was coming from a customer.
Comment 11 Nir Yechiel 2016-04-12 09:31:17 UTC 
While our strategy is to move to Octavia in compliant with upstream, our current assessment shows that it will take more time to get it mature and ready for production use. 

As a mid-term solution we are aiming to provide a better HA solution for LBaaS v2 using the HAProxy driver. This work is planned for Newton based on these two bugs:

https://bugs.launchpad.net/neutron/+bug/1565511
https://bugs.launchpad.net/neutron/+bug/1565801
Comment 16 Assaf Muller 2016-06-04 01:21:01 UTC 

*** This bug has been marked as a duplicate of bug 1326224 ***