Bug 1550720

Summary: Can't specifically modify haproxy timeouts per service
Product: Red Hat OpenStack Reporter: rosingh
Component: puppet-tripleoAssignee: Michele Baldessari <michele>
Status: CLOSED ERRATA QA Contact: Udi Shkalim <ushkalim>
Severity: medium Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: augol, bperkins, chjones, dvd, jjoyce, jschluet, marjones, michele, mkrcmari, pkomarov, rhos-maint, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-8.3.2-0.20180327181745.40b702f.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:46:51 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:

Description rosingh 2018-03-01 21:23:38 UTC
Description of problem:
Not able to change client/server time-out for cinder/nova/keystone alone.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 rosingh 2018-03-01 21:30:45 UTC
we'd like a way to configure haproxy timeouts per service, like in:
$mysql_listen_options = {
'option'         => [ 'tcpka', 'httpchk' ],
'timeout client' => '90m',
'timeout server' => '90m',
'stick-table'    => 'type ip size 1000',
'stick'          => 'on dst',
'maxconn'        => $mysql_max_conn
 }

Comment 8 Michele Baldessari 2018-03-24 07:16:15 UTC
Queens backport merged, moving to POST

Comment 12 errata-xmlrpc 2018-06-27 13:46:51 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/RHEA-2018:2086