Current Series Release Notes

New Features

  • Added a new configuration option image_conversion_disable to disallow conversion between image disk format and volume format when doing certain operations. This can prevent performance problems on a cinder-volume node due to the large amount of system resources consumed during image conversion. The default value is False, which corresponds to Cinder’s current behavior to always attempt image conversion.

    This option affects three Block Storage API calls:

    • Upload volume to image: POST /v3/volumes/{volume_id}/action with the os-volume_upload_image action. This call will result in a 400 (Bad Request) response when an image disk_format that would require conversion is requested.

    • Create a volume: POST /v3/volumes with an imageRef attribute in the request body. This will result in a 202 (Accepted) response, but if the image’s disk_format would require conversion to be written to the volume, the volume will go to error status.

    • Reimage a volume: POST /v3/volumes/{volume_id}/action with the os-reimage action. This call will result in a 202 (Accepted) response, but if the image’s disk_format would require conversion to be written to the volume, the volume will go to error status.

    In the latter two cases, an end user can determine what happened by using the Messages API, which can be accessed using the cinderclient or openstackclient.

  • Seagate driver: Added support for get_driver_options api call

  • Lenovo driver: Return additional configuration options from get_driver_options call

Upgrade Notes

  • Support for MySQL 5.5 has been dropped.

  • Python 3.6 & 3.7 support has been dropped. The minimum version of Python now supported is Python 3.8.

  • The storage_protocol treats all variants of the protocol name as the same regarding matches, so for example using FC, fc, or fibre_channel will be treated equally in the scheduler, be it when filtering using the volume type’s extra specs or when using filter and goodness functions.

    The storage protocol reporting via the REST API will be now the same for them all, using the preferred naming, FC, NVMe-oF, iSCSI, NFS…

    If your deployment uses storage_protocol to differentiate between backends that use the same protocol but report it using different variants, be aware that they will no longer be differentiated.

Bug Fixes

  • Fixed a CHAP authentication issue while trying to attach an iSCSI volume using the NetApp ONTAP driver. Please refer to the Launchpad bug #1914639 for more details.

  • Bug #1929223: Fixed HTTPS certificate validation was disabled in PowerFlex connector.

  • RBD driver bug #1942210: When creating a volume from a snapshot, the operation could fail due to an uncaught exception being raised during a check to see if the backend Ceph installation supported the clone v2 API. The driver now handles this situation gracefully.

  • Bug #1944577: Managing a volume to an encrypted type was never a good idea because there was no way to specify an encryption key ID so that the volume could be used. Requests to manage a volume to an encrypted volume type now result in an invalid request response.

  • IBM DS8000 Driver Bug #1951046: Fixed detach issue for multi-attach volumes. Detach the volume without deleting the host until attachment count is zero.

  • NetApp ONTAP driver bug #1955057: Fixed the function get_ontap_version on Cinder NetApp driver, now it returns a tuple of integers instead of a string.

  • IBM Spectrum Virtualize family driver Bug #1960314: Fixed resize issue for GMCV volumes which are a part of a consistency group(CG).

  • IBM Spectrum Virtualize family driver Bug #1960315: Fixed delete and resize volume issues in during reverse replication and added support to extend the volume for failover scenarios.

  • IBM Spectrum Virtualize Family driver: Bug #1961548: Optimize lsvdisk and lssystem calls to reduce the computational time for creating GMCV volumes.

  • Bug #1965847: Fixed issue where importing a backup record for a backup_id that currently existed had the unfortunate side effect of deleting the existing backup record.

  • IBM Spectrum Virtualize family driver Bug #1966639: Fixed resize issue in reverse replication for the volumes which are a part of a consistency group(CG).

  • IBM Spectrum Virtualize Family driver: Bug #1968159: Fix for retype failure for replicated volume-type. Controlling chfcmap call for rc_controlled fcmap for replication-type volumes during retype operation.

  • Bug #1968170: Fixed the message created when nova fails to reimage the volume.

  • Bug #1970768: Fixed status of temporary volumes when creating backups and reverting to a snapshot, preventing accidental manual deletion of those resources.

  • RBD driver bug #1916843: Fixed rpc timeout when backing up RBD snapshot. We no longer flatten temporary volumes and snapshots.

  • Bug #1969366: Fixed reporting of cacheable capability by drivers.

  • Fix NetApp iSCSI and FC driver issues with custom initiator groups. (bug 1697490).

  • Bug #1966103: Fixed inconsistent behavior of storage_protocol among different backends that report variants of the protocol name, such as FC, fc, fibre_channel.

  • Bug #1901188: Fix unnecessary migration on retype when QoS has the same elements in both types.

  • HPE 3PAR driver Bug #1958122: Fixed issue of multi-detach operation in multi host environment.

  • NetApp ONTAP: Fix check QoS minimum support for SVM scoped account. See: Bug #1924798.

  • Bug #1951982: Fixed cloning of encrypted volumes not using multipathing to change the encryption key used on the new volume.

  • Bug #1951977: Fixed backup create and restore not using multipath configuration when attaching the volume.

  • Kaminario driver bug #1951981: Fixed create volume from volume or snapshot not using multipath configuration.


Welcome to the Yoga release of the OpenStack Block Storage service (cinder). With this release, the Block Storage API version 3 has reached microversion 3.68. The cinder team would like to bring the following points to your attention. Details may be found throughout this document.

  • Microversion 3.67 is introduced as a marker to indicate that any instance of the Block Storage API 3.67 or greater treats a project_id in the URL as optional. This change is backward compatible: the API can handle legacy URLs containing a project_id as well as URLs without a project_id. This is the case regardless of what microversion specified in a request. See the “New Features” section for details.

  • Microversion 3.68 introduces a new volume action, os-reimage, that allows a user to replace the current content of a specified volume with the data of a specified image supplied by the Image service (glance). See the “New Features” section for details.

  • Some new backend storage drivers have been added, and many current drivers have added features and fixed bugs.