Post installation, Horizon login page simple states "Something went wrong!".

Bug #1233929 reported by Kevin Carter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Cloud Archive
Undecided
Unassigned

Bug Description

Post installation, the Horizon Login page will not load without the use of Debug mode being enabled in "/etc/openstack-dashboard/local_settings.py".

* The installation was done On Precise with all available updates being installed prior to the installation.
* Both the proposed packages as well as the updates were enabled in the apt sources list.

While I am assuming this is a horizon specific issue, it may very well be related to "openstack-dashboard" Here is the Openstack Dashboard Package that I have installed.
openstack-dashboard:
  Installed: 1:2013.2~b3-0ubuntu1~cloud0

Openstack-Dashboard is being used with Apache2. The Apache error logs do not reveal anything. I have also attempted to run the openstack-dashboard using manage.py::

/usr/share/openstack-dashboard/manage.py runserver <LOCAL-IP>:80 --verbosity=4 --traceback --insecure --settings 'openstack_dashboard.settings' --nothreading

While running in this mode, the verbose output shows a "500" error but does not provide any other information. When Debug mode is enabled the dashboard loads fine under both the local command and apache2; I am able to navigate freely although its very slow.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: python-django-horizon 1:2013.2~b3-0ubuntu1~cloud0 [origin: Canonical]
ProcVersionSignature: Ubuntu 3.2.0-49.75-virtual 3.2.46
Uname: Linux 3.2.0-49-virtual x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
CrashDB: cloud_archive
Date: Wed Oct 2 01:44:38 2013
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: horizon
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kevin Carter (kevin-carter) wrote :
description: updated
Revision history for this message
Kevin Carter (kevin-carter) wrote :

This issue is resolved if you set :

ALLOWED_HOSTS = ['*']

In the local_settings.py file found in /etc/openstack_dashboard
It seems this setting is required in newer versions of Django.

Changed in cloud-archive:
status: New → Invalid
Revision history for this message
Sunnyvale CI Bot (sunnyvale-ci-bot) wrote :

We currently patch the shipped settings file to include this:

+# By default, validation of the HTTP Host header is disabled. Production
+# installations should have this set accordingly. For more information
+# see https://docs.djangoproject.com/en/dev/ref/settings/.
+ALLOWED_HOSTS = '*'

Does this not work as-is, or was it removed post-installation from the default config by some deployment tool?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers