| Summary: | Heat API timeout in haproxy should be more than default 60 seconds | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ramon Acedo <racedoro> |
| Component: | rhosp-director | Assignee: | Angus Thomas <athomas> |
| Status: | CLOSED WORKSFORME | QA Contact: | Omri Hochman <ohochman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | bperkins, dbecker, jslagle, mburns, mcornea, morazi, rhel-osp-director-maint, therve |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-28 10:33: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: | |
Timeout is 10 minutes now. |
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.