HAproxy timeouts are too short
Bug #1621299 reported by
Emilien Macchi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Invalid
|
Medium
|
Emilien Macchi | ||
Bug Description
I'm currently trying to deploy tripleo/scenario001 job which contains Glance and RBD backend (Ceph).
Because we install all overcloud on one single virtual machine in OpenStack Infra, we're running with low resources and Glance image upload might take longer than 1 minute.
The default HAproxy timeout value is 1 minute for client and server. It might be too short.
Revision history for this message
| Emilien Macchi (emilienm) wrote | #1 |
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Emilien Macchi (emilienm) |
| milestone: | none → newton-rc1 |
Revision history for this message
| Emilien Macchi (emilienm) wrote | #2 |
| Changed in tripleo: | |
| importance: | High → Medium |
| Changed in tripleo: | |
| status: | Triaged → Invalid |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on puppet-tripleo (master) | #3 |
To post a comment you must log in.
Note that Fuel already faced this issue: https:/
They solved it by increasing the default timeout to client 3h and server 3h.