030fd71390
Cinder's volume create API does not support overriding the project_id and user_id, and it silently igores those API inputs. Cinder always uses the project and user info in the keystone identity associated with the API request. If a user specifies the --project or --user option, the volume create is aborted and a CommandError exception is raised. This prevents a volume from being created, but without the desired project/user values. A user wishing to specify alternate values can still do so using identity overrides (e.g. --os-username, --os-project-id). Story: 2002583 Task: 22192 Change-Id: Ia9f910ea1b0e61797e8c8c463fa28e7390f15bf9
16 lines
704 B
YAML
16 lines
704 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The ``--project`` and ``--user`` options for the ``volume create``
|
|
command have been deprecated. They are deprecated because Cinder's
|
|
volume create API ignores the corresponding API inputs.
|
|
fixes:
|
|
- |
|
|
Fix ``volume create`` by removing two broken options. The ``--project``
|
|
and ``--user`` options were intended to specify an alternate project
|
|
and/or user for the volume, but the Volume service's API does not
|
|
support this behavior. This caused the volume to be created, but
|
|
without the expected project/user values. However, an alternate
|
|
project and/or user may be specified using identity overrides (e.g.
|
|
--os-username, --os-project-id).
|