Debian Codegraph @

releasenotes/notes/allow-deleting-__DEFAULT__-type-d35dfb5d89760b9b.yaml

raw
1 ---
2 upgrade:
3 - |
4 The ``default_volume_type`` configuration option is now required
5 to have a value. The default value is ``__DEFAULT__``, so you
6 should see no change in behavior whether or not you have set a
7 value for ``default_volume_type``. See
8 `Bug #1886632 <https://bugs.launchpad.net/cinder/+bug/1886632>`_
9 for more information about this change.
10
11 fixes:
12 - |
13 `Bug #1886632 <https://bugs.launchpad.net/cinder/+bug/1886632>`_:
14 The system defined ``__DEFAULT__`` volume type is now treated as
15 a regular volume-type and may be updated or deleted. Since the
16 configured ``default_volume_type`` cannot be deleted, however,
17 the ``__DEFAULT__`` volume type may not be deleted if it is the
18 value of that configuration option.
19
20 other:
21 - |
22 Beginning with the Train release, untyped volumes (that is, volumes with
23 no volume-type) have been disallowed. To facilitate this, a
24 ``__DEFAULT__`` volume-type was included as part of the Train database
25 migration. In this release, handling of the default volume-type has been
26 improved:
27
28 * The ``default_volume_type`` configuration option is required to have a
29 value. The default value is ``__DEFAULT__``.
30 * A request to delete the currently configured ``default_volume_type``
31 will fail. (You can delete that volume-type, but you cannot do it
32 while it is the value of the configuration option.)
33 * There must always be at least one volume-type defined in a Cinder
34 installation. This is enforced by the type-delete call.
35 * If the ``default_volume_type`` is misconfigured (that is, if the value
36 refers to a non-existent volume-type), requests that rely on the
37 default volume-type (for example, a volume-create request that does
38 not specify a volume-type) will result in a HTTP 500 response.