Bug 1029775
Summary: | Horizon requires python-pbr at runtime | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Matthias Runge <mrunge> |
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: | afazekas, aortega, apevec, hateya, jpichon, mrunge, rvaknin, yeylon |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-django-horizon-2013.2-4.el6ost | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-20 00:35:25 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: | |
Embargoed: |
Description
Matthias Runge
2013-11-13 07:55:14 UTC
When installing horizon on a separate host (not doing all-in-one installs), you'll get the "Something went wrong page". After installing python-pbr and restart the webserver as well, everything is fine. This will require to change add to the spec accordingly: sed -i '/setuptools_git/d' setup.py sed -i s/REDHATNOVAVERSION/%{version}/ nova/version.py sed -i s/REDHATNOVARELEASE/%{release}/ nova/version.py # Remove the requirements file so that pbr hooks don't add it # to distutils requiers_dist config rm -rf {test-,}requirements.txt tools/{pip,test}-requires Verified: python-django-horizon-2013.2-5.el6ost.noarch Verification Steps: =================== 1. Installed openstack via packstack with a dedicated host to populate horizon (Comment #1). 2. Verified that /usr/lib/python2.6/site-packages/horizon/version.py does not contain import pbr.version 3. Browsed Horizon via http://<IP_ADDRESS>/dashboard. tested OK. *** Bug 1039368 has been marked as a duplicate of this bug. *** 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 |