Bug 1520799

Summary:	Incorrect cookie statement for haproxy in composable roles.
Product:	Red Hat OpenStack	Reporter:	Nikhil Shetty <nshetty>
Component:	puppet-tripleo	Assignee:	Michele Baldessari <michele>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	high	Docs Contact:
Priority:	high
Version:	10.0 (Newton)	CC:	amcleod, bperkins, cfeist, chjones, fdinitto, jjoyce, jschluet, michele, mkrcmari, ojanas, pmannidi, rhos-maint, rohara, slinaber, tvignaud, ushkalim
Target Milestone:	z9	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-tripleo-5.6.8-14.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the cookie set in the horizon stanza for haproxy was incorrect and connections to horizon may be loadbalanced to the wrong server. With this update, the cookie now points to the correct server.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-17 16:54:10 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:

Description Nikhil Shetty 2017-12-05 07:51:40 UTC

Description of problem:
When creating Composable Roles with haproxy behind httpd. 

Version-Release number of selected component (if applicable): OSP 10


How reproducible:

- In an Deployment with composable roles with Director 
- loadbalancer exists on a separate cluster to the systemd controlled services
- It seems the haproxy listen directive for horizon is tagging each of the servers with the same cookie. this causes a single node to have Max no of requests.

Actual results: A single Server gets majority of the Request 


Expected results: The Load should be distributed equally across all Servers.

Comment 4 Chris Jones 2017-12-07 09:19:36 UTC

We can hang on to this BZ for OSP10 - but we already have an upstream fix in progress at https://bugzilla.redhat.com/show_bug.cgi?id=1485446

Comment 8 Michele Baldessari 2018-07-23 11:48:55 UTC

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

Comment 19 errata-xmlrpc 2018-09-17 16:54:10 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://access.redhat.com/errata/RHBA-2018:2670