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

Bug 1415828

Summary:	Backport: [RFE] [Neutron] [LBaaS v2] Add process monitor for haproxy
Product:	Red Hat OpenStack	Reporter:	Nir Magnezi <nmagnezi>
Component:	openstack-neutron-lbaas	Assignee:	Nir Magnezi <nmagnezi>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	amedeo.salvati, amuller, apevec, bperkins, dcadzow, jschluet, jthomas, lhh, lpeer, mlopes, nlevinki, nyechiel, oblaut, pablo.iranzo, sclewis, tfreger
Target Milestone:	z2	Keywords:	FeatureBackport, FutureFeature, OtherQA, Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-lbaas-9.1.0-3.el7ost	Doc Type:	Enhancement
Doc Text:	This enhancement implements ProcessMonitor in the HaproxyNSDriver class (v2) to use the external_process module, which allows it to monitor and respawn the haproxy processes as needed. The LBaaS agent (v2) will load options related to external_process in order to take a configured action when the HAproxy process dies unexpectedly.	Story Points:	---
Clone Of:	1326224
Clones:	1431152 (view as bug list)		Environment:
Last Closed:	2017-02-23 16:34:25 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:	1326224
Bug Blocks:	1046780, 1273812, 1431152

Comment 4 Nir Magnezi 2017-02-15 13:41:15 UTC

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 6 errata-xmlrpc 2017-02-23 16:34:25 UTC

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://rhn.redhat.com/errata/RHBA-2017-0314.html