| Summary: | tenant chooser doesn't work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Cole Robinson <crobinso> | ||||
| Component: | python-django-horizon | Assignee: | Pádraig Brady <pbrady> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | crobinso, markmc, mrunge | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-03 08:42:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Cole Robinson
2012-03-07 23:06:00 UTC
Created attachment 568779 [details]
keystone error
While using dashboard, the attached trace back is appearing in the keystone logfile
so keystone is returning a http 500 to dashboard (if this is the same problem)
Derek, there's two parts I think. One is the issue you mention, I was hitting that too even with upstream and submitted a patch for it: https://review.openstack.org/5088 The other seems to be a UI issue in that all fancy drop downs don't seem to be working at all. So even with my patch things don't work IIRC. Upstream has this UI bit fixed but I haven't bisected yet. That review was rejects, and essex was supposed to have a fix... but it didnt. So I submitted a new fix: https://review.openstack.org/#/c/6579/ That review expired, but it fixed things for me on F17, so might still be worth a push. Also: https://bugs.launchpad.net/horizon/+bug/982595 I have never seen those problems in current 2012.2.x versions. I guess it was fixed upstream. |