RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1271433 - Horizon fails to load
Summary: Horizon fails to load
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: rdo-manager
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: Liberty
Assignee: Giulio Fidente
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-14 00:40 UTC by Marius Cornea
Modified: 2016-04-18 06:57 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-0.8.7-1.el7
Clone Of:
Environment:
Last Closed: 2016-03-30 23:02:37 UTC
Embargoed:


Attachments (Terms of Use)
horizon traceback (2.10 KB, text/plain)
2015-10-14 00:40 UTC, Marius Cornea
no flags Details
debug trace.html (229.39 KB, text/html)
2015-10-15 14:40 UTC, John Trowbridge
no flags Details


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 235418 0 None None None Never

Description Marius Cornea 2015-10-14 00:40:10 UTC
Created attachment 1082653 [details]
horizon traceback

Description of problem:
I'm running an RDO Manager deployment with 3 ctrls and 1 compute and overcloud Horizon is throwing a 500 error. 

Version-Release number of selected component (if applicable):
python-django-horizon-8.0.0.0-rc1.el7.centos.noarch
openstack-dashboard-8.0.0.0-rc1.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run a deployment with 3 controllers and 1 compute with network isolation
2. Access Horizon on the public VIP

Actual results:
Something went wrong! screen

Expected results:
Login prompt shows up

Additional info:
Attaching tracebak.

Comment 1 Mike Orazi 2015-10-14 20:45:14 UTC
Matthias,

Can we get some help understanding the root cause here?

Comment 2 Matthias Runge 2015-10-15 06:04:25 UTC
Unfortunately, the traceback does not tell anything useful.

First rule, to get a more usable trace would be to enable debug:
/etc/openstack-dashboard/local_settings 
set DEBUG = True
and restart httpd

Probably unrelated, there has been a rc2 release, which had many bugs fixed. I strongly recommend to test that version.

Comment 3 John Trowbridge 2015-10-15 14:40:53 UTC
Created attachment 1083298 [details]
debug trace.html

Comment 4 John Trowbridge 2015-10-15 14:43:19 UTC
Looks like we are configuring memcached for horizon incorrectly. I verified that if I put a single value for CACHES['LOCATION'] like:

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',



        'LOCATION': '192.0.2.18:11211',


    }
}


I was able to get a login page.

Comment 5 Alan Pevec 2015-10-15 15:01:01 UTC
Extracting from debug trace what does not work:
CACHES	
{'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',
             'LOCATION': ['192.0.2.18:11211',
                          '192.0.2.17:11211',
                          '192.0.2.19:11211']}}

Comment 6 Alan Pevec 2015-10-15 15:11:55 UTC
Notes from IRC:
python-django-1.8.4-1.el7.noarch
https://docs.djangoproject.com/en/1.8/topics/cache/
<trown> gfidente: confirmed setting .memcached.MemcachedCache allowed it to start with list
<gfidente> should be https://review.openstack.org/235418

Comment 7 Matthias Runge 2015-10-15 19:07:32 UTC
CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
        'LOCATION': '127.0.0.1:11211',
    }
}

is correct, but be sure to install
python-memcached

Comment 13 Alan Pevec 2015-10-19 15:13:45 UTC
Move to modified only when build is done in CBS.


Note You need to log in before you can comment on or make changes to this bug.