Admin->Volumes page in Horizon times out
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Confirmed
|
Wishlist
|
MOS Nova | |||
6.0.x |
Won't Fix
|
Medium
|
MOS Horizon | |||
6.1.x |
Won't Fix
|
Medium
|
MOS Horizon | |||
7.0.x |
Won't Fix
|
Medium
|
Paul Karikh | |||
8.0.x |
Won't Fix
|
Wishlist
|
MOS Nova | |||
9.x |
Won't Fix
|
Wishlist
|
MOS Nova |
Bug Description
One of environment in facing problems with listing of volumes (all volumes) via horizon; section in admin -> volumes.
Using standard HAProxy approach - connection in terminated before it could be serve to customer (timeout) but using direct connection to apache request is being served.
Time it takes for such request to finish is 1307084ms.
Other sections of horizon works correctly, for example: page admin->instances is generated in few seconds.
Number of active nova instances: 620
Number of cinder volumes: 700
MOS: 4.0
From log files (dashboard) I can see that for each instance "GET" request is being made while list of all volumes are being generated (from horizon).
Time it takes for each such request it 3 seconds.
... dashboard-
... dashboard-
... dashboard-
... dashboard-
... dashboard-
# time nova list --all-tenants
real 0m10.501s
user 0m0.532s
sys 0m0.128s
# time cinder list --all-tenants
real 0m23.020s
user 0m0.396s
sys 0m0.088s
# dpkg -l |grep -i dashboard
ii murano-dashboard 0.4.fuel4.0~mira8 murano-dashboard
ii openstack-dashboard 1:2013.
ii openstack-
description: | updated |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → Medium |
affects: | fuel → mos |
Changed in mos: | |
milestone: | 6.1 → none |
tags: | added: horizon |
summary: |
- Horizon - Issue with Admin->Volumes + Admin->Volumes page in Horizon times out |
tags: | added: customer-found |
Changed in mos: | |
milestone: | none → 6.1 |
Changed in mos: | |
status: | Confirmed → Won't Fix |
milestone: | 6.1 → 7.0 |
no longer affects: | mos/7.0.x |
Changed in mos: | |
status: | Won't Fix → Confirmed |
Changed in mos: | |
assignee: | MOS Horizon (mos-horizon) → Paul Karikh (pkarikh) |
tags: | added: enhancement |
tags: | added: mos-nova |
tags: | added: wontfix-low |
tags: | added: 10.0-reviewed |
"Using standard HAProxy approach - connection in terminated before it could be serve to customer (timeout) but using direct connection to apache request is being served.
Time it takes for such request to finish is 1307084ms."
I guess half of an hour for request completion should not be considered as a SUCCESS. Shouldn't it be considered as a bug for Horizon?