diff options
Diffstat (limited to 'releasenotes')
19 files changed, 182 insertions, 13 deletions
diff --git a/releasenotes/notes/backup-sparse-f396b35bfe17332e.yaml b/releasenotes/notes/backup-sparse-f396b35bfe17332e.yaml new file mode 100644 index 000000000..a9731cb62 --- /dev/null +++ b/releasenotes/notes/backup-sparse-f396b35bfe17332e.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + `Bug #2007615 <https://bugs.launchpad.net/cinder/+bug/2007615>`_: + the restore operation of the Cinder backup service now restores into + sparse volumes, if possible. So, operators no longer need more space + than used previously when they restore from a disaster. diff --git a/releasenotes/notes/bug-1981420-dell-powermax-fix-for-force-flag-9320910dfbf998d2.yaml b/releasenotes/notes/bug-1981420-dell-powermax-fix-for-force-flag-9320910dfbf998d2.yaml new file mode 100644 index 000000000..aa626ac5c --- /dev/null +++ b/releasenotes/notes/bug-1981420-dell-powermax-fix-for-force-flag-9320910dfbf998d2.yaml @@ -0,0 +1,8 @@ +--- +fixes: + - | + `Dell PowerMax Driver Bug #1981420 <https://bugs.launchpad.net/cinder/+bug/1981420>`_: + Fixed issue faced while creating synchronous volume which was caused by + incorrect handling of the force flag. This is corrected by checking volume + type extra specs for the value of "force_vol_edit" parameter along with the + "force" parameter. diff --git a/releasenotes/notes/bug-2008017-netapp-fix-native-threads-04d8f58f4c29b03d.yaml b/releasenotes/notes/bug-2008017-netapp-fix-native-threads-04d8f58f4c29b03d.yaml new file mode 100644 index 000000000..c6b05987d --- /dev/null +++ b/releasenotes/notes/bug-2008017-netapp-fix-native-threads-04d8f58f4c29b03d.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - | + `Bug #2008017 <https://bugs.launchpad.net/cinder/+bug/2008017>`_: Fixed + NetApp NFS driver to never spawn a native thread avoid thread starvation + and other related issues. diff --git a/releasenotes/notes/bug-2008931-hpe-keyerror-on-migration-71d31e6c0a8ab0d9.yaml b/releasenotes/notes/bug-2008931-hpe-keyerror-on-migration-71d31e6c0a8ab0d9.yaml new file mode 100644 index 000000000..1e5f09f86 --- /dev/null +++ b/releasenotes/notes/bug-2008931-hpe-keyerror-on-migration-71d31e6c0a8ab0d9.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + HPE 3PAR driver `bug #2008931 + <https://bugs.launchpad.net/cinder/+bug/2008931>`_: Fixed + issue when performing migrate volume operation when `comment` + attribute is missing from the volume. diff --git a/releasenotes/notes/db-resource-indexes-8010c9a881277503.yaml b/releasenotes/notes/db-resource-indexes-8010c9a881277503.yaml new file mode 100644 index 000000000..4d062c258 --- /dev/null +++ b/releasenotes/notes/db-resource-indexes-8010c9a881277503.yaml @@ -0,0 +1,24 @@ +--- +upgrade: + - | + The ``cinder-manage db sync`` command for this verison of cinder will add + additional database indexes. Depending on database size and complexity, + this will take time to complete for every single index to be created. On + MySQL or MariaDB, these indexes will only be created if an index does not + already exist with the same name: + + * ``groups_deleted_project_id_idx`` + * ``group_snapshots_deleted_project_id_idx`` + * ``volumes_deleted_project_id_idx`` + * ``volumes_deleted_host_idx`` + * ``snapshots_deleted_project_id_idx`` + * ``backups_deleted_project_id_idx`` + + An example of the SQL commands to generate these indexes can be found + in the `specific troubleshooting guide + <htts://docs.openstack.org/cinder/latest/admin/ts-db-cpu-spikes.html>`_. +fixes: + - | + `Bug #1952443 <https://bugs.launchpad.net/cinder/+bug/1952443>`_: Improve + performance for creating volume from image, listing volumes, snapshots, + backups, groups, and group_snapshots. diff --git a/releasenotes/notes/dell-powerflex-bugfix-1998136-self-signed-certificates-62e3cb444ab7ff2b.yaml b/releasenotes/notes/dell-powerflex-bugfix-1998136-self-signed-certificates-62e3cb444ab7ff2b.yaml new file mode 100644 index 000000000..550390a89 --- /dev/null +++ b/releasenotes/notes/dell-powerflex-bugfix-1998136-self-signed-certificates-62e3cb444ab7ff2b.yaml @@ -0,0 +1,10 @@ +--- +fixes: + - | + Dell PowerFlex driver `bug #1998136 + <https://bugs.launchpad.net/cinder/+bug/1998136>`_: + When using self signed certificates, the option + sent to os-brick via the connection_properties was + not correctly handled. It has now been fixed by + adding the 'verify_certificate' and 'certificate_path' + to the driver when initializing the connection. diff --git a/releasenotes/notes/hitachi-vsp-add-hostgroup-name-format-option-4c8e4a5ddd69b9bd.yaml b/releasenotes/notes/hitachi-vsp-add-hostgroup-name-format-option-4c8e4a5ddd69b9bd.yaml index 20ed2cb80..e96aa8b28 100644 --- a/releasenotes/notes/hitachi-vsp-add-hostgroup-name-format-option-4c8e4a5ddd69b9bd.yaml +++ b/releasenotes/notes/hitachi-vsp-add-hostgroup-name-format-option-4c8e4a5ddd69b9bd.yaml @@ -3,6 +3,7 @@ features: - | Hitachi driver: Add a config option ``hitachi_group_name_format`` for hostgroup name format. + When using this option, users can specify the name format of host groups or iSCSI targets. Rules of the format: @@ -12,22 +13,25 @@ features: * The specified value must start with ``HBSD-``. * You can use the following variables: - * ``{wwn}``: FC driver only. This is replaced with the smallest - WWPN of the WWPNs of the connecting node. - * ``{ip}``: iSCSI driver only. This is replaced with the IP address of - the connecting node. - * ``{host}``: This is replaced with the host name of the connecting node. + ``{wwn}`` + `FC driver only.` This is replaced with the smallest + WWPN of the WWPNs of the connecting node. + ``{ip}`` + `iSCSI driver only.` This is replaced with the IP address of + the connecting node. + ``{host}`` + This is replaced with the host name of the connecting node. * You can use each variable in the specified value no more than once. * The specified value must include the following variables: - * FC driver: ``{wwn}`` - * iSCSI driver: ``{ip}`` + * FC driver: ``{wwn}`` + * iSCSI driver: ``{ip}`` * The maximum length of a specified value is as follows: - * FC driver: 64 - * iSCSI driver: 32 + * FC driver: 64 + * iSCSI driver: 32 * In the length calculation, use the following values as the length of each variable: @@ -46,8 +50,10 @@ features: iSCSI targets do not exceed the maximum length. If you specify this parameter, it is recommended that you specify ``True`` - for the hitachi_group_create parameter to collect necessary + for the ``hitachi_group_create`` parameter to collect necessary information automatically. + Examples: + * FC driver: ``HBSD-{host}-{wwn}`` * iSCSI driver: ``HBSD-{host}-{ip}`` diff --git a/releasenotes/notes/hitachi-vsp-add-multi-pool-4c4589b93399e641.yaml b/releasenotes/notes/hitachi-vsp-add-multi-pool-4c4589b93399e641.yaml index 817e9a567..0223d7a5b 100644 --- a/releasenotes/notes/hitachi-vsp-add-multi-pool-4c4589b93399e641.yaml +++ b/releasenotes/notes/hitachi-vsp-add-multi-pool-4c4589b93399e641.yaml @@ -1,5 +1,12 @@ --- features: -- | - Supported multi-pool for Hitachi driver and OEM storage driver. - + - | + Supported multi-pools for Hitachi driver and OEM storage drivers. +upgrades: + - | + Hitachi driver and OEM storage drivers: Changed option names + ``hitachi_pool`` to ``hitachi_pools``, + ``hpexp_pool`` to ``hpexp_pools`` and + ``nec_v_pool`` to ``nec_v_pools``. + The options ``hitachi_pool``, ``hpexp_pool`` and ``nec_v_pool`` + are deprecated.
\ No newline at end of file diff --git a/releasenotes/notes/hitachi-vsp-fix-keyerr-when-backend-down-a5a35b15dc8f1132.yaml b/releasenotes/notes/hitachi-vsp-fix-keyerr-when-backend-down-a5a35b15dc8f1132.yaml new file mode 100644 index 000000000..f996280d9 --- /dev/null +++ b/releasenotes/notes/hitachi-vsp-fix-keyerr-when-backend-down-a5a35b15dc8f1132.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - | + Hitachi, NEC V, HPE XP drivers `bug #2004140 + <https://bugs.launchpad.net/cinder/+bug/2004140>`_: Fixed + ``KeyError`` when a backend is down.
\ No newline at end of file diff --git a/releasenotes/notes/hitachi-vsp-support-dedup-comp-4e27d95b34681f66.yaml b/releasenotes/notes/hitachi-vsp-support-dedup-comp-4e27d95b34681f66.yaml new file mode 100644 index 000000000..da8392b62 --- /dev/null +++ b/releasenotes/notes/hitachi-vsp-support-dedup-comp-4e27d95b34681f66.yaml @@ -0,0 +1,7 @@ +--- +features: + - | + Hitachi driver: Support data deduplication and compression, by storage assist. + The feature can be worked, if user enable deduplication and compression + for the DP-pool, by Configuration Manager REST API, and set the extra + spec ``hbsd:capacity_saving`` to ``deduplication_compression`` diff --git a/releasenotes/notes/hpe-3par-convert-to-base-vol-delete-snap-a460a4b1c419804a.yaml b/releasenotes/notes/hpe-3par-convert-to-base-vol-delete-snap-a460a4b1c419804a.yaml new file mode 100644 index 000000000..e087e3353 --- /dev/null +++ b/releasenotes/notes/hpe-3par-convert-to-base-vol-delete-snap-a460a4b1c419804a.yaml @@ -0,0 +1,11 @@ +--- +fixes: + - | + HPE 3PAR driver `Bug #1994521 <https://bugs.launchpad.net/cinder/+bug/1994521>`_: + Fixed: While performing a delete snapshot (s1) operation, the volumes (v2) + dependent on the snapshot (s1) are converted to base volumes. This + operation fails if these dependent volumes (v2) have their own dependent + snapshots (s2). The errors during the failure were vague and not helpful. + With this release, we added conditions to fail this operation early and + also added useful error message. + diff --git a/releasenotes/notes/ibm-svf-delete-volume-flag-support-for-deletevolumegroup-4224db1ca798a3bf.yaml b/releasenotes/notes/ibm-svf-delete-volume-flag-support-for-deletevolumegroup-4224db1ca798a3bf.yaml new file mode 100644 index 000000000..ca6eb86f8 --- /dev/null +++ b/releasenotes/notes/ibm-svf-delete-volume-flag-support-for-deletevolumegroup-4224db1ca798a3bf.yaml @@ -0,0 +1,6 @@ +--- +features: + - | + IBM Spectrum Virtualize Family driver: Added `--delete-volumes` flag + support for delete volumegroup operation. After adding support, + the volumes can optionally be deleted when the volume group is deleted. diff --git a/releasenotes/notes/nvmeof-premature-terminate-conn-63e3cc1fd1832874.yaml b/releasenotes/notes/nvmeof-premature-terminate-conn-63e3cc1fd1832874.yaml new file mode 100644 index 000000000..0cb120fc1 --- /dev/null +++ b/releasenotes/notes/nvmeof-premature-terminate-conn-63e3cc1fd1832874.yaml @@ -0,0 +1,7 @@ +--- +fixes: + - | + nvmeof target `bug #1966513 + <https://bugs.launchpad.net/cinder/+bug/1966513>`_: Fixed + LVM failing on terminate_connection if the connecting host doesn't have an + iSCSI initiator name setup, for example if LVM is using the nvmet target. diff --git a/releasenotes/notes/nvmet-multipath-d35f55286f263e72.yaml b/releasenotes/notes/nvmet-multipath-d35f55286f263e72.yaml new file mode 100644 index 000000000..7e4f0db5a --- /dev/null +++ b/releasenotes/notes/nvmet-multipath-d35f55286f263e72.yaml @@ -0,0 +1,16 @@ +--- +features: + - | + nvmet target driver: Added support to serve volumes on multiple addresses + using the ``target_secondary_ip_addresses`` configuration option. This + allows os-brick to iterate through them in search of one connection that + works, and once os-brick supports NVMe-oF multipathing it will be + automatically supported. + + This requires that ``nvmeof_conn_info_version`` configuration option is set + to ``2`` as well. +deprecations: + - | + Configuration option ``iscsi_secondary_ip_addresses`` is deprecated in + favor of ``target_secondary_ip_addresses`` to follow the same naming + convention of ``target_ip_address``. diff --git a/releasenotes/notes/nvmet-shared-targets-20ed7279ef29f002.yaml b/releasenotes/notes/nvmet-shared-targets-20ed7279ef29f002.yaml new file mode 100644 index 000000000..2357c4fdb --- /dev/null +++ b/releasenotes/notes/nvmet-shared-targets-20ed7279ef29f002.yaml @@ -0,0 +1,6 @@ +--- +features: + - | + nvmet target driver: Added support for shared subsystems/targets using the + ``lvm_share_target`` configuration option. Defaults to non shared, e.g., + each volume has its own subsystem/target. diff --git a/releasenotes/notes/rbd-total_capacity-60f10b45e3a8c8ea.yaml b/releasenotes/notes/rbd-total_capacity-60f10b45e3a8c8ea.yaml new file mode 100644 index 000000000..1efa65097 --- /dev/null +++ b/releasenotes/notes/rbd-total_capacity-60f10b45e3a8c8ea.yaml @@ -0,0 +1,8 @@ +--- +fixes: + - | + RBD driver `bug #1960206 + <https://bugs.launchpad.net/cinder/+bug/1960206>`_: Fixed + ``total_capacity`` reported by the driver to the scheduler on Ceph clusters + that have renamed the ``bytes_used`` field to ``stored``. (e.g., `Nautilus + <https://docs.ceph.com/en/nautilus/releases/nautilus/#upgrade-compatibility-notes>`_). diff --git a/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml b/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml new file mode 100644 index 000000000..0b11c4a48 --- /dev/null +++ b/releasenotes/notes/remove-multiattach-request-param-4444e02533f919da.yaml @@ -0,0 +1,20 @@ +--- +fixes: + - | + `Bug #2008259 <https://bugs.launchpad.net/cinder/+bug/2008259>`_: + Fixed the volume create functionality where non-admin users were + able to create multiattach volumes by providing the `multiattach` + parameter in the request body. Now we can only create multiattach + volumes using a multiattach volume type, which is also the + recommended way. +other: + - | + Removed the ability to create multiattach volumes by specifying + `multiattach` parameter in the request body of a volume create + operation. This functionality is unsafe, can lead to data loss, + and has been deprecated since the Queens release. + The recommended method for creating a multiattach volume is to + use a volume type that supports multiattach. By default, volume + types can only be created by the operator. Users who have a need + for multiattach volumes should contact their operator if a suitable + volume type is not available. diff --git a/releasenotes/source/2023.1.rst b/releasenotes/source/2023.1.rst new file mode 100644 index 000000000..d1238479b --- /dev/null +++ b/releasenotes/source/2023.1.rst @@ -0,0 +1,6 @@ +=========================== +2023.1 Series Release Notes +=========================== + +.. release-notes:: + :branch: stable/2023.1 diff --git a/releasenotes/source/index.rst b/releasenotes/source/index.rst index b26aeca4d..36c9fa080 100644 --- a/releasenotes/source/index.rst +++ b/releasenotes/source/index.rst @@ -6,6 +6,7 @@ Cinder Release Notes :maxdepth: 1 unreleased + 2023.1 zed yoga xena |