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

Bug 1726733

Summary:	Default amphora timeouts too high for production environments
Product:	Red Hat OpenStack	Reporter:	Carlos Goncalves <cgoncalves>
Component:	openstack-tripleo-heat-templates	Assignee:	Carlos Goncalves <cgoncalves>
Status:	CLOSED ERRATA	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	amcleod, igallagh, jschluet, mburns, michjohn, twilson
Target Milestone:	z11	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.4.1-22.el7ost	Doc Type:	Enhancement
Doc Text:	This enhancement provides default Octavia timeouts that are suitable for production environments, and the following new heat parameters to override the defaults: * OctaviaConnectionMaxRetries * OctaviaBuildActiveRetries * OctaviaPortDetachTimeout	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-10 11:18:32 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 Carlos Goncalves 2019-07-03 15:14:29 UTC

The default amphora timeouts are too high for production environments.

The defaults today in OSP 13 are:
[haproxy_amphora] connection_max_retries = 300
[haproxy_amphora] build_active_retries = 300

Better defaults would be:

[haproxy_amphora]/connection_max_retries = 120
[haproxy_amphora]/build_active_retries = 120

Overriding these defaults should also be possible via Director parameters.

One other setting that should be possible to override via Director is [networking]/port_detach_timeout. The default value should not be changed for thee time being at least.

Comment 9 errata-xmlrpc 2020-03-10 11:18:32 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-2020:0760