| Summary: | Horizon: Cannot log-in. Exception Value: 'User' object has no attribute 'services_region' | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Gilles Dubreuil <gdubreui> |
| Component: | python-django-openstack-auth | Assignee: | Ami Jeain <ajeain> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0 | CC: | ajeain, ddomingo, hateya, mrunge, yeylon |
| Target Milestone: | beta | Keywords: | Rebase, Triaged |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-django-openstack-auth-1.1.2-1.el6ost | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-20 00:21:35 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
Gilles Dubreuil
2013-08-23 11:02:07 UTC
I wanted to confirm that this is still effecting package : Name : python-django-openstack-auth Arch : noarch Version : 1.1.2 Release : 1.el6 Size : 78 k Repo : installed From repo : epel-openstack Running Horizon as a single server, in verbose mode with all settings yields this error: [23/Oct/2013 03:17:04] "POST /auth/login/ HTTP/1.1" 403 1006 Horizon started with: /usr/share/openstack-dashboard/manage.py runserver --insecure --settings=openstack_dashboard.settings --pythonpath=/usr/share/openstack-dashboard/ -v 3 --traceback x.x.x.x:80 This does not show any additional failures and or stack traces besides what was already mentioned. Presently the workaround in downgrading the AUTH package does still work. Kevin, the last sentence makes me very suspicious, if you cleared your cookies after updating the package AND restarting httpd? Hey Matthias, thanks for the reply. It seems that when upgrading, which was what i was testing, all I needed to do was a simple restart of Apache. While I thought I had done that initially, it seems on m subsequent upgrade tests everything is working as expected. Thank you again. Kevin, glad it worked for you and the solution was that simple. Auto adding >= MODIFIED bugs to beta 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 |