Fuel for OpenStack

Error message when starting deployment on large environment

Bug #1546703 reported by Mikhail Chernik on 2016-02-17

This bug report is a duplicate of: Bug #1569859: Nailgun doesn't respond during a minute after starting deploy of 200 nodes. Edit Remove

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Fuel for OpenStack	Confirmed	Medium	Fuel Sustaining	Fuel for OpenStack 10.0
8.0.x	Won't Fix	Medium	MOS Maintenance	Fuel for OpenStack 8.0-updates
Mitaka	Confirmed	Medium	Fuel Sustaining	Fuel for OpenStack 9.2

Bug Description

When starting environment deployment on 200 nodes, message "A server error has occurred" appears on UI (screen-shot attached).

However, this error does not affect deployment process.

The reason is that Keep-Alive connection is timed out and nailgun receives 504 error from nginx:
[root@fuel ~]# zgrep error /var/log/docker-logs/nginx/error_nailgun.log.1.gz | grep -v SSL
2016/02/17 18:32:54 [error] 310#0: *23422 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.194.211, server: localhost, request: "PUT /api/clusters/1/changes HTTP/1.1", upstream: "uwsgi://10.20.0.2:8001", host: "172.16.44.10:8443", referrer: "https://172.16.44.10:8443/"
2016/02/17 18:33:28 [error] 310#0: *29820 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.194.211, server: localhost, request: "GET /api/nodes/allocation/stats?_=1455731484515 HTTP/1.1", upstream: "uwsgi://10.20.0.2:8001", host: "172.16.44.10:8443", referrer: "https://172.16.44.10:8443/"
2016/02/17 18:33:28 [error] 310#0: *29130 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.194.211, server: localhost, request: "GET /api/notifications?_=1455731484516 HTTP/1.1", upstream: "uwsgi://10.20.0.2:8001", host: "172.16.44.10:8443", referrer: "https://172.16.44.10:8443/"
2016/02/17 18:33:36 [error] 310#0: *29821 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.194.211, server: localhost, request: "GET /api/nodes?cluster_id=1&_=1455731484517 HTTP/1.1", upstream: "uwsgi://10.20.0.2:8001", host: "172.16.44.10:8443", referrer: "https://172.16.44.10:8443/"

Tags: