OpenStack Dashboard (Horizon)

Project selection is not working

Bug #997635 reported by Marco CONSONNI
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
Undecided
Unassigned

Bug Description

Conditions when I started the test:

0) Login as administrator
1) Add a user named "User1" created with Horizon, primary project "openstackDemo" (openstackDemo is preexistent)
2) Add a project named "aNewProject" with Horizon. Project is enabled

--- Steps

1) Go to Projects and select "Modify Users" for "aNewProject"
2) Select "User1" and "Add To Project" with Role "admin"
3) Logout

4) Login as "User1"

Project selection dropdown does not list "openstackDemo", it only shows "aNewProject"

I also re-login as administrator and removed "User1" from "aNewProject". After that, if a reconnect as "User1", the dropdown shows "openstackDemo", only.

Revision history for this message
Devin Carlen (devcamcar) wrote :

Marking as incomplete until we can reproduce this. Thanks for the report.

Changed in horizon:
status: New → Incomplete
milestone: none → folsom-1
importance: Undecided → High
assignee: nobody → Nebula (nebula)
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

Bumping from milestone due to inactivity.

Changed in horizon:
importance: High → Undecided
milestone: folsom-1 → none
Revision history for this message
Tyler North (tylern-u) wrote :

I can confirm this bug also affects me as well.
From what I can tell, when you log in the project assigned automatically is the project with the highest ID that the user is a member off
For example:
user-test_user with a primary project : openstackDemo
Two projects
openstackDemo (ID 5)
projectDemo(ID 6, with test_user as a member)
since 6 is the highest ID, upon logging in as test_user, the project is set to projectDemo

Changed in horizon:
status: Incomplete → Confirmed
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

@tyler: you are correct, however this bug report is not about the "default project" not being the one the user is logged into. That's a known bug with keystone not sending back the user's default project when retrieving a user token.

@marco: I cannot reproduce this bug. I've followed your steps exactly. I've even tried it with both admin and member roles on the projects. The project dropdown list always returns the correct set of projects for me. This is with current Horizon and Keystone master, installed via Devstack. If the bug you were describing were taking place it would be due to Keystone sending back an improperly scoped token. However, I'm not seeing that bug (which was fixed in Diablo, and fixed again in Essex after Keystone made some changes in Essex).

Changed in horizon:
status: Confirmed → Invalid
Revision history for this message
Marco CONSONNI (marco-consonni) wrote :

Guys, thanks for your notes.
At the moment I don't have access to the systems I installed OpenStack on, therefore I'm not able to reproduce or try other stuff.
Just a couple of things about the software I'm using.

I installed everything following the instructions I found in this manual http://docs.openstack.org/trunk/openstack-compute/install/content/index.html and not using Devstack. I don't know if the problem originates from this....

Curtis Hovey (sinzui)
Changed in horizon:
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.