Bug 1387362 - Heat API timeout in haproxy should be more than default 60 seconds
Summary: Heat API timeout in haproxy should be more than default 60 seconds
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 17:09 UTC by Ramon Acedo
Modified: 2017-09-28 10:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-28 10:33:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ramon Acedo 2016-10-20 17:09:09 UTC
A call to Heat API times out if it takes more than 1 minute in an operation.

This is happening in an undercloud with 8 vCPUs and 12GB of RAM set up with https.

As an example, a call made from:'openstack --debug stack resource list overcloud -n3' in this setup takes 1 minute and 15 seconds but after 1 minute it fails. Usually the error is something like this:

HTTPException: ERROR: <html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

As a workaround I added "timeout server 7200s" in the relevant section in haproxy.cfg

listen heat_api
  bind 192.168.3.2:13004 transparent ssl crt /etc/pki/tls/certs/undercloud-192.168.3.2.pem
  bind 192.168.3.3:8004 transparent
  mode http
  http-request set-header X-Forwarded-Proto https if { ssl_fc }
  http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
  rsprep ^Location:\ http://192.168.3.2(.*) Location:\ https://192.168.3.2\1
  server 192.168.3.1 192.168.3.1:8004 check fall 5 inter 2000 rise 2
  timeout server 7200s


As an additional note, a VM with the same specs but configuring director without https didn't timeout but now I haven't got that VM anymore to do a like for like comparison.

Comment 2 Thomas Hervé 2017-09-28 10:33:32 UTC
Timeout is 10 minutes now.


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