In environment with big amount of nodes, fuel CLI fails hitting timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Oleksiy Molchanov |
Bug Description
--- Environment ---
* MOS: 9.2
* 185 slave nodes
* Fuel node is a VM with:
- 20 vCPUs
- 192 Gb RAM
--- Description ---
On executing fuel commands, we are facing "504 gateway timeout" error
[root@fuel ~]# fuel deployment --env 1 --download --dir /var/lib/
504 Server Error: Gateway Time-out for url: http://
<head><title>504 Gateway Time-out<
<body bgcolor="white">
<center><h1>504 Gateway Time-out<
<hr><center>
</body>
</html>
)
Out of the box the default value of uwsgi_read_timeout (60 seconds) is used.
Increasing the timeout to 120 seconds has helped in this particular environment.
Please check if the default value in MOS needs to be tuned to suit production environment (or there is some other way to fix it)
Changed in fuel: | |
milestone: | 9.x-updates → 9.2-mu-9 |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | MOS Maintenance (mos-maintenance) → Oleksiy Molchanov (omolchanov) |
sla1 for 9.0-updates