Bug 1326224 – [RFE] [Neutron] [LBaaS v2] Add process monitor for haproxy

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1326224 - [RFE] [Neutron] [LBaaS v2] Add process monitor for haproxy

Summary:	[RFE] [Neutron] [LBaaS v2] Add process monitor for haproxy

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-neutron-lbaas (Show other bugs)
Sub Component:
Version:	9.0 (Mitaka)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	Upstream M3
Target Release:	11.0 (Ocata)
Assigned To:	Nir Magnezi
QA Contact:	Toni Freger
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature, OtherQA, Triaged

Duplicates:	1269981 (view as bug list)
Depends On:
Blocks:	1273812 1046780 1415828 1431152
	Show dependency tree / graph

Reported:	2016-04-12 04:19 EDT by Nir Magnezi
Modified:	2017-05-17 15:28 EDT (History)
CC List:	18 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	This enahncement implements the 'ProcessMonitor' class in the 'HaproxyNSDriver' class (v2), This class utilizes the 'external_process' module to monitor and respawn HAProxy processes if and when needed. The LBaaS agent (v2) loads 'external_process' related options and take a configured action when HAProxy dies unexpectedly.
Story Points:	---
Clone Of:
Clones:	1415828 (view as bug list)
Environment:
Last Closed:	2017-05-17 15:28:33 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1565801	None	None	None	2016-04-12 04:19 EDT
OpenStack gerrit	327966	None	None	None	2016-06-13 08:27 EDT
OpenStack gerrit	344658	None	None	None	2016-09-01 15:55 EDT
OpenStack gerrit	345263	None	None	None	2016-07-24 16:29 EDT
Red Hat Product Errata	RHEA-2017:1245	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory	2017-05-17 19:01:50 EDT

Groups: None (edit)

Description Nir Magnezi 2016-04-12 04:19:07 EDT

Description of problem:
=======================
Bug 1325861 (launchpad #1565511) aims to solve cases where the lbaas agent goes offline.
To have a complete high-availability solution for lbaas agent with haproxy running in namespace, we would also want to handle a case where the haproxy process itself stopped.

This[1] neutron spec offers the following approach:
"We propose monitoring those processes, and taking a configurable action, making neutron more resilient to external failures."

[1] http://specs.openstack.org/openstack/neutron-specs/specs/juno/agent-child-processes-status.html

Comment 2 Assaf Muller 2016-06-03 21:21:01 EDT

*** Bug 1269981 has been marked as a duplicate of this bug. ***

Comment 10 Nir Yechiel 2016-09-01 10:53:17 EDT

Both patches look to be merged.

Comment 11 Assaf Muller 2016-09-01 15:55:32 EDT

https://review.openstack.org/#/c/327966/ was reverted, adding https://review.openstack.org/#/c/344658/ as an external tracker.

Comment 18 Assaf Muller 2017-01-13 15:15:51 EST

Patch has been merged upstream.

Comment 23 Nir Magnezi 2017-02-15 08:40:32 EST

How to test:
============
1. Create a Loadbalancer
2. Create a Listener
3. Create Pool and memebers
4. Verify loadbalancing functionality.
5. Kill the haproxy process
6. Wait for ~30 sec and see if it respawns.
7. Redo step #4

Comment 28 Alexander Stafeyev 2017-03-23 07:27:16 EDT

https://review.openstack.org/#/c/344658/21/neutron_lbaas/drivers/haproxy/namespace_driver.py@379 
fits what I have in my deployment. 

Verifying

Tnx

Comment 29 errata-xmlrpc 2017-05-17 15:28:33 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1245

Note You need to log in before you can comment on or make changes to this bug.