Openstack dashboard doesn't work after primary controller shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Committed
|
High
|
Max Yatsenko | ||
5.1.x |
Fix Committed
|
High
|
Max Yatsenko |
Bug Description
api: '1.0'
astute_sha: 702af3db6f5bca9
auth_required: true
build_id: 2014-11-12_21-56-33
build_number: '3'
feature_groups:
- mirantis
fuellib_sha: 7d711bb3d2572d5
fuelmain_sha: e5e534ade6f3765
nailgun_sha: bbc9dfe78a0c330
ostf_sha: 64cb59c681658a7
production: docker
release: 5.1.1
After killing of primary controller node Horizon became broken, it showed the following message after log in:
"Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator."
I enabled debug mode in dashboard settings and got the error traceback:
http://
Full page with debug info is attached.
Changed in fuel: | |
assignee: | nobody → MOS Horizon (mos-horizon) |
Changed in mos: | |
status: | Confirmed → In Progress |
The problem may be related to the fact that we django does not tolerate memcached node death. The best solution is to fix this in django itself introducing connection pooling for django memcached backend. But I am not sure we can do this in 5.1.1.