Current Series Release Notes

16.0.0.0rc1-127

New Features

  • Nimble driver now supports discard.

  • Added an included_domain_ips option to the Dell EMC SC driver. This option takes a comma separated list of target IP addresses listed under the fault domains to whitelisted. This option only applies to the ISCSI driver.

  • We can now limit the number of concurrent backup/restore operations that a Cinder backup service can perform using the backup_max_operations configuration option.

  • The NFS driver now supports the creation of encrypted volumes.

  • Add Dell EMC PowerStore Storage Driver (iSCSI, FC).

  • The oslo.middleware /healthcheck is now activated by default in the Cinder api-paste.ini. Operators can use it to configure HAproxy or the monitoring of Cinder APIs. Edit the api-paste.ini file and remove any healthcheck entries to disable this functionality.

  • New Cinder Hitachi driver based on REST API for Hitachi VSP storages.

  • PowerMax for Cinder driver now supports Port Group and Port load balancing when attaching Nova Compute instances to volumes on the backend PowerMax.

  • Add reverting to snapshot support in Pure Storage Cinder driver.

Upgrade Notes

  • The fix for Bug #1823200 requires os-brick version 3.1.0 or greater.

  • Due to the fix for Bug #1740950, the host_name field in any object in the attachments array of the volume detail response is populated only when the call is made in an administrative context. Otherwise, its value is the JSON null value. This is consistent with prior API behavior, as it has always been possible for the value of that field to be null.

  • IBM Spectrum Virtualize Family (previously known as Storwize) driver cannot delete volume which has host mapping in some rare cases while code_level of IBM Spectrum Virtualize Family storage lower than 7.7.0.0. Please upgrade to latest code to avoid this kind of issue.

  • Dell EMC VxFlex OS has been rebranded to PowerFlex. The driver cinder.volume.drivers.dell_emc.vxflexos.driver.VxFlexOSDriver has been renamed to cinder.volume.drivers.dell_emc.powerflex.driver.PowerFlexDriver. Although in this release the volume manager will recognize the old driver name, that functionality will be removed in the Wallaby release, and thus we recommend that you update the driver name in cinder.conf at your earliest convenience.

    Existing vxFlex OS configuration options will continue to work in this release, but this functionality will be removed in the Wallaby release. Thus all driver configuration options that start with vxflexos should be updated to powerflex in your cinder.conf as soon as possible.

    Before the Rocky release, this driver was named cinder.volume.drivers.dell_emc.scaleio.driver.ScaleIODriver. That name was deprecated in the Rocky release. In this release, the pre-Rocky name for this driver is no longer recognized and support for configuration options beginning with sio has been removed.

    The online documentation has been updated to reflect these changes.

Security Issues

  • It was possible under certain circumstances for the host name of an instance to be leaked in the volume detail response. This has been fixed in the current release. The host_name field in any object in the attachments array of the volume detail response is populated only when the call is made in an administrative context. Otherwise, its value is the JSON null value.

Bug Fixes

  • Add Python 3 support to the Brocade Zone Manager driver. (bug #1888548).

  • Fix AttributeError on the Brocade ZM driver when using setting REST_HTTP or REST_HTTPS as the fc_southbound_protocol option and an exception is raised by the client (Bug #1866860).

  • Bug #1823200: This release contains an updated Dell EMC VxFlex OS driver. It must be used with os-brick version 3.1.0 or greater and requires that a new configuration file be deployed on compute nodes, cinder nodes, and anywhere you would perform a volume attachment in your deployment. See the Dell EMC VxFlex OS (ScaleIO) Storage driver documentation for details about the configuration file, and see OSSN-0086 for more information about the security vulnerability.

  • Fix the bug that a volume retyped from other volume type to replicated or multiattach type cannot be enabled replicated or multiattach in rbd driver. (Bug #1828386)

  • Fixed bug #1859652 to allow retyping an attached volume to SolidFire.

  • Cinder no longer allows an incremental backup to be created while having the parent backup in another project.

  • Fix bug #1874134, allowing an iSCSI or FCP volume to be extended to a size up to 16TB regardless of its original size, even if it’s attached to an instance.

  • Fixed bug #1874541 Where a ZeroDivisionError was hapenning when the SolidFire driver tried to update cluster capabilities.

  • Bug #1875570: Fixed issue with NFS backend where the image-volume cache was never used to create a volume, even when the cache was enabled.

  • Bug #1879578: A regression in the Train release caused Cinder to assign the default volume type too aggressively when a volume type was not specified in a volume-create request. As a result, some alternative methods of specifying the volume type were ignored and the default type (either configured by the operator or the system default) would be assigned.

    This release restores the intended behavior, which is described as follows:

    If a volume_type is not specified when a volume is created, Cinder tries to infer the volume type from other information in the volume-create request:

    • if a source_volid is supplied in the request, the volume type is inferred from the source volume’s volume type

    • if a snapshot_id is supplied in the request, the volume type is inferred from the volume type associated with the snapshot

    • if an imageRef is supplied in the request, and the image has a cinder_img_volume_type image property, the volume type is inferred from the value of that image property

    Otherwise, the volume type is the default volume type configured by the operator, and if no volume type is so configured, the volume type is the system default volume type, namely, __DEFAULT__.

    When a volume type is specified explicitly in a volume-create call, Cinder will use the specified type. If the specified type cannot be assigned due to a conflict with other parameters in the volume-create call, however, the call will result in a 400 (Bad Request) response.

  • Bug #1886222: Fixed an issue with creating a snapshot on an NFS backend if the snapshot name is not specified.

  • Bug #1873738: RBD Driver: Added cleanup for residue destination file if the copy image to encrypted volume operation fails.

  • Fix HPE 3PAR driver issue where volumes that were live migrated to it would end up being inaccessible. We would no longer be able to use the volume for any operation, such as attach, detach, delete, snapshot, etc. (bug 1697422)

  • Fix the HPE 3PAR driver’s attempt to rename the backend volume after it was migrated. If the original volume resides on the same 3PAR backend then the pre and post migration volume names are swapped. Otherwise, the newly migrated volume is renamed to match the original name. (bug 1858119)

  • Bug #1740950: the host_name field in any object in the attachments array of the volume detail response is populated only when the call is made in an administrative context. Otherwise, its value is the JSON null value.

  • Fix unique_fqdn_network configuration option for the Kaminario driver, as it was being ignored when defined in the driver section, which used to work. (Bug #1886042).

  • Fix leaving mapped volumes on offline volume migration and revert to snapshot operations failure. (bug 1880971).

  • NetApp ONTAP: Fixes bug 1839384 Detaching any instance from multiattached volume terminates connection. Now the connection is terminated only if there’re no other instances using the same initiator.

  • PowerMax Driver - Concurrent live migrations can sometimes fail when one thread deletes a storage group that another thread may need.

  • Fix revert to snapshot not working for non admin users when using the snapshot’s name (bug #1889758).

Other Notes

  • PowerMax driver - the minimum version of Unisphere for PowerMax required for Victoria is 9.2, so all the latest 92 REST endpoints will be used.