Bug 1020363

Summary:	Horizon fails to function due to an ImportError
Product:	Red Hat OpenStack	Reporter:	Nir Magnezi <nmagnezi>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	aortega, ddomingo, hateya, jpichon, mrunge, yeylon
Target Milestone:	beta
Target Release:	4.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	python-django-horizon-2013.2-1.el6ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-20 00:29:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nir Magnezi 2013-10-17 14:10:34 UTC

Description of problem:
=======================
Via packstack, I installed Horizon as a standalone node.
It fails to function due to an ImportError.

Version-Release number of selected component (if applicable):
=============================================================
puddle: 2013-10-15.1
python-django-horizon-2013.2-0.15.rc2.el6ost.noarch

How reproducible:
=================
1/1

Steps to Reproduce:
===================
1. Install OpenStack via packstack, Make sure that the node you configure to run Horizon is only used with  CONFIG_HORIZON_HOST.
2. Try to login.
3.


Actual results:
===============
At first, I got internal server error.
I restarted httpd and tried to browse horizon once again.

Login failed with the following errors:
ImportError: Could not import settings 'openstack_dashboard.settings' (Is it on sys.path?): No module named eventlet    


Expected results:
=================
Horizon should function properly.

Comment 4 Nir Magnezi 2013-11-11 14:08:33 UTC

Verified NVR: python-django-horizon-2013.2-3.el6ost.noarch

Followed the 'Steps to Reproduce' in Comment #0
Result: Horizon works with no errors.

Comment 7 errata-xmlrpc 2013-12-20 00:29:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html