Red Hat Bugzilla – Full Text Bug Listing
|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>|
|Version:||17||CC:||crobinso, markmc, mrunge|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-12-03 03:42:15 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Cole Robinson 2012-03-07 18:06:00 EST
python-django-horizon-2012.1-0.1.rc1.fc18.noarch If a user has multiple associated tenants, the tenant chooser under the 'project' panel on the left hand side doesn't work. It might be a UI issue since the thing doesn't seem to react to clicking at all, and not a data issue on the other end.
Comment 1 Derek Higgins 2012-03-08 19:31:52 EST
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)
Comment 2 Cole Robinson 2012-03-08 22:02:19 EST
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.
Comment 3 Cole Robinson 2012-04-15 17:26:06 EDT
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/
Comment 4 Cole Robinson 2012-05-29 19:36:56 EDT
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
Comment 5 Matthias Runge 2012-12-03 03:42:15 EST
I have never seen those problems in current 2012.2.x versions. I guess it was fixed upstream.