error when create a new user with its role is _member_

[guomin.lizte]

In dashboard panel ,when I create a new user ,its role assigned to _member_, on the top of right corner ,the dashboard displays that "Error: Unable to add user to primary project." Actually, the user is created successfully.

[Dolph Mathews (dolph)]

I'm not sure if Keystone or Horizon is at fault here, so I've added both as Incomplete.

The user may have been created successfully, but keystone will also attempt to assign the _member_ role to the user in the user's default tenant (the user.tenant_id attribute in v2, or user.default_project_id in v3). Did the role assignment take place successfully in Keystone? (is there a record of the assignment in the keystone backend?)

Is horizon failing on a different call somewhere? Is there a traceback available?

[Julie Pichon (jpichon)]

I believe this is a duplicate of bug 1260439, which is fixed in Juno and was backported to Icehouse, it should be released with 2014.1.2 in a couple of weeks. The user is created successfully and with the correct role, the error message happens because we're trying to assign a role that the user already has (I think it used to be Keystone didn't set a default role by default).

[guomin.lizte (limin6886)]

It actually so as Julie said。Through the log，I can see it first use user_create (), in this fuction, _member_ is assigned; if we assigned the same role in dashbord pannel when create a user, add_role_to_user() will return exception.Conflict

[Julie Pichon (jpichon)]

I'm marking as duplicate, feel free to remove the 'duplicate' relationship to reopen this if you disagree. Thank you!

[Julie Pichon (jpichon)]

To correct my comment in #2 it's because Horizon used to have its own 'Member' role but we switched the default to '_member_' instead, to avoid confusing users over having 2 "member" definitions and be in sync with Keystone (bug 1264228).