cinder only supports deriving a user and project id from auth context
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
New
|
Undecided
|
Unassigned | ||
| python-cinderclient |
Fix Committed
|
Undecided
|
Rajat Dhasmana | ||
| python-openstackclient |
New
|
Undecided
|
Unassigned | ||
Bug Description
In the python bindings for creating a volume there are arguments for specifying a user_id and project_id [1], this exists for many resources (volumes and consistency groups).
:param user_id: User id derived from context
:param project_id: Project id derived from context
These are then added to the request body. However, as the docstring indicates, it seems cinder API will never make use of these values. The user_id and project_id is always derived from the auth context [2]. Additionally, the cinder CLI also does not provide a user id or project id to make use of these arguments.
* Why supply these arguments in cinderclient if they are never used?
* Was there ever a plan to allow an admin to create a volume (or cinder resource) for someone else? As it stands now, that would not be possible.
[1] https:/
| Steve Martinelli (stevemar) wrote | #1 |
| John Griffith (john-griffith) wrote | #2 |
| Steven Pisarski (spisarski) wrote | #3 |
| Changed in python-cinderclient: | |
| assignee: | nobody → Rajat Dhasmana (whoami-rajat) |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-cinderclient (master) | #4 |
| Changed in python-cinderclient: | |
| status: | New → In Progress |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on python-cinderclient (master) | #5 |
| Rajat Dhasmana (whoami-rajat) wrote | #6 |
| Changed in python-cinderclient: | |
| status: | In Progress → Fix Committed |
Adding OSC since we (incorrectly) assumed that the user_id and project_id arguments were being used.