Nailgun doesn't respond during a minute after starting deploy of 200 nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Fuel Toolbox | ||
8.0.x |
Won't Fix
|
High
|
Sergii Rizvan | ||
Mitaka |
Fix Released
|
High
|
Fuel Toolbox |
Bug Description
Detailed bug description:
After clicking "deploy changes" nailgun service doesn't respond during a minute.
from UI we can see "Nailgun is Unavailable" message (screen is attached). After a minute we car reach UI and can see that deplyment started.
from /var/log/
atop at the time: http://
Steps to reproduce:
1. Configure env with 200 nodes and click "deploy changes"
Expected results:
UI shows that deployment started
Actual result:
UI shows error, but after a minute we can reach UI and see that deplotment is actually started
Reproducibility:
reproduced each time
Workaround:
Hasn't been found yet
Impact:
UI looks bad
Description of the environment:
Operation system: Ubuntu
Versions of components: mos9.0 and fuel agent from mos10.0
Reference architecture: 3 controllers, 20 computes+ceph, 178 computes
Network model: vxlan+Neutron L2 population+DVR
Related projects installed: no
Additional information:
fuel-9.0-188
Log folder from fuel node is here: http://
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 9.0 |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-python |
description: | updated |
description: | updated |
tags: | added: team-enhancements |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Ilya Kutukov (ikutukov) |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
tags: | added: release-notes |
Changed in fuel: | |
assignee: | Ilya Kutukov (ikutukov) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Bulat Gaifullin (bgaifullin) → Ilya Kutukov (ikutukov) |
status: | In Progress → Fix Committed |
tags: | added: 9.1-proposed |
tags: |
added: release-notes-done removed: release-notes |
the deployment graph serialisation is doing in parallel thread, but request waits until this job will be done.
the request should not wait completion of deployment graph serialisation.