| 1 |
--- |
| 2 |
fixes: |
| 3 |
- | |
| 4 |
`Bug #1879578 <https://bugs.launchpad.net/cinder/+bug/1879578>`_: |
| 5 |
A regression in the Train release caused Cinder to assign the default |
| 6 |
volume type too aggressively when a volume type was not specified in |
| 7 |
a volume-create request. As a result, some alternative methods of |
| 8 |
specifying the volume type were ignored and the default type (either |
| 9 |
configured by the operator or the system default) would be assigned. |
| 10 |
|
| 11 |
This release restores the intended behavior, which is described as |
| 12 |
follows: |
| 13 |
|
| 14 |
If a ``volume_type`` is not specified when a volume is created, Cinder |
| 15 |
tries to infer the volume type from other information in the |
| 16 |
volume-create request: |
| 17 |
|
| 18 |
* if a ``source_volid`` is supplied in the request, the volume type |
| 19 |
is inferred from the source volume's volume type |
| 20 |
* if a ``snapshot_id`` is supplied in the request, the volume type |
| 21 |
is inferred from the volume type associated with the snapshot |
| 22 |
* if an ``imageRef`` is supplied in the request, and the image has |
| 23 |
a ``cinder_img_volume_type`` image property, the volume type is |
| 24 |
inferred from the value of that image property |
| 25 |
|
| 26 |
Otherwise, the volume type is the default volume type configured by |
| 27 |
the operator, and if no volume type is so configured, the volume type |
| 28 |
is the system default volume type, namely, ``__DEFAULT__``. |
| 29 |
|
| 30 |
When a volume type is specified explicitly in a volume-create call, Cinder |
| 31 |
will use the specified type. If the specified type cannot be assigned due |
| 32 |
to a conflict with other parameters in the volume-create call, however, the |
| 33 |
call will result in a 400 (Bad Request) response. |