Bug 862330

Summary: Unable to select project in left gutter "Project" tab pull-down
Product: Red Hat OpenStack Reporter: Dan Yocum <dyocum>
Component: python-django-horizonAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Nir Magnezi <nmagnezi>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0 (Essex)CC: apevec, markmc, mrunge
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2012.2.1-2.el6ost.noarch Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 16:32:06 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 Dan Yocum 2012-10-02 16:27:53 UTC
Description of problem:

As any user, admin or normal, clicking on the Project pulldown in the left gutter doesn't show the other projects the user is a member of.

Version-Release number of selected component (if applicable):

Essex

How reproducible:

Always

Steps to Reproduce:
1. Click on the "Project" tab in the left gutter
2. Click on the "Project" pulldown
3.
  
Actual results:

A single project is displayed and no other projects are offered as choices

Expected results:

The admin user should at the very least be able to select from the projects admin, demo, and service.

Additional info:

Comment 2 Mark McLoughlin 2012-12-07 09:48:04 UTC
Sounds like a bug, for sure. Worth reproducing in Essex so we understand the issue and then confirming it's fixed in Folsom.

Comment 3 Yaniv Kaul 2012-12-07 10:10:24 UTC
Nir - please reproduce (see comment 2 above).

Comment 4 Matthias Runge 2012-12-07 12:05:13 UTC
I have seen this reported as an issue somewhere and I'm sure, it is fixed in Folsom.

Comment 7 Dan Yocum 2012-12-18 23:14:14 UTC
If the following patch is in Folsom, then yes, it is fixed.  This is the bug you're thinking of:

https://github.com/fedora-openstack/keystone/commit/ffd7a4bbad5b43171238f586eb47b360cbc4430e

This patch also fixes this bug, too:

https://bugzilla.redhat.com/show_bug.cgi?id=862322

Comment 8 Alan Pevec 2013-01-10 16:32:06 UTC
(In reply to comment #7)
> If the following patch is in Folsom, then yes, it is fixed.  This is the bug
> you're thinking of:
> 
> https://github.com/fedora-openstack/keystone/commit/
> ffd7a4bbad5b43171238f586eb47b360cbc4430e

Yes, that's in RHOS Folsom