2024.1 Series Release Notes

24.2.0

New Features

  • Added a new cinder-manage command to handle the situation where database purges would not complete due to the volumes table holding references to deleted services. The new command makes sure that all volumes have a reference only to the correct service_uuid, which will allow old service records to be purged from the database.

    Command: cinder-manage volume update_service

  • When Cinder creates a new cinder-volume service, it now also immediately updates the service_uuid for all volumes associated with that cinder-volume host. In some cases, this was preventing the database purge operation from completing successfully.

Bug Fixes

  • Bug #2027532: Fixed Cinder API HTTP 500 when issuing a volume list and sorting by a boolean field (i.e. “bootable”).

  • Hitachi driver bug #2072317: Fix potential data-loss due to a network issue during a volume deletion.

  • Hitachi driver bug #2071697 <https://bugs.launchpad.net/cinder/+bug/2071697>’_: Fix to set correct object ID as LDEV nickname when running host-assisted migration with ``retype` or migration commands.

  • Hitachi driver bug #2063317: Fix test scripts to avoid failing by unexpected response from pseudo REST API server

  • HPE 3PAR driver Bug #2068795: Fixed: Perform login before invoking getWsApiVersion

  • RBD driver: No longer copy the RBD source volume image to a temporary file when uploading a volume to an image.

24.1.0

Security Issues

  • Images in the qcow2 format with an external data file are now rejected with an ImageUnacceptable error because such images could be used in an exploit to expose host information. Given that qcow2 external data files were never supported by Cinder, this change should have no impact on users. See Bug #2059809 for details.

Bug Fixes

  • Dell PowerMax driver bug #2034937: Fixed

    This change is to update the live migration ability in environments using PowerMax. In the previous 2023.1 version, the live migration fails without a pool name. This update adds the ability of live migration without a pool name.

  • Bug #2058596: Fixed broken backup_swift_service_auth=True which made Swift backup driver consistently fail during object data access.

  • Bug #2059809: Fixed issue where a qcow2 format image with an external data file could expose host information. Such an image is now rejected with an ImageUnacceptable error if it is used to create a volume. Given that qcow2 external data files were never supported by Cinder, the only use for such an image previously was to attempt to steal host information, and hence this change should have no impact on users.

  • Bug #2031897: Fixed issues for volume backups with the Ceph driver where failures of the first process (“rbd export-diff”) were not caught. Instead, only the return code of the second process (“rbd import-diff”) was recognized.

    This change also preserves the stderr that was lost previously in order to ease debugging.

24.0.0

New Features

  • Dell PowerFlex driver: Enabled Cinder volume active/active support. This allows users to configure Dell PowerFlex backends in Cinder-clustered environments. Note that active/active support is specific to OpenStack volume services as PowerFlex storage replication is asynchronous.

  • Dell EMC PowerMax driver: Added SRDF powermax:disable_protected_snap volume-type extra-spec property for the purpose of avoiding overconsumption on both source and target storage arrays.

    An operator may enable this functionality by creating a specific volume type with the property:

    "powermax:disable_protected_snap": "<is> True"

    When disabled (which is the default and current behaviour), a replicated source volume will be protected with a snapshot of the same volume type.

    When enabled, snapshots of replicated source volumes will be treated as regular, non-replicated devices.

  • Add the new os-extend_volume_completion volume action, which the Nova compute agent can use to notify Cinder that it has finished handling the volume-extended external server event.

  • Fujitsu ETERNUS DX driver: Added support to extend a volume on RAID Group using CLI.

    Revised the ‘Extend Volume’ process on the RAID Group to improve processing speed as follows:

    • When extending a volume created on ThinProvisionPool, the process will still use SMI-S for volume extension.

    • When extending a volume created on RaidGroup, the process has been updated to use CLI for volume extension.

  • NetApp iSCSI/FCP drivers: NetApp space allocation feature allows ONTAP and host to see the actual space correctly when host deletes data. It also notifies the host when the LUN cannot accept write data due to lack of space on the volume, and makes the LUN read-only (rather than going offline). This feature can be enabled or disabled on cinder volumes by using volume type extra specs with the netapp:space_allocation property.

  • Open-E JovianDSS driver: revert-to-snapshot has been removed.

  • Dell PowerMax driver: Enabled support for Active/Active to both FC and iSCSI driver. This allows users to configure Dell PowerMax backends in clustered environments.

  • Pure Storage driver: Allow synchronously replicated volumes to be created during a replication failover event. These will remain viable volumes when the replication is failed back to its original state.

Upgrade Notes

  • Infinidat driver: support has been removed for pre-v3.0 InfiniBox systems. These versions are end of life and have not been supported for a long time.

  • Dell PowerMax Driver: introduced a new configuration option, snapvx_unlink_symforce, to address Bug #2045230. See the Bug Fixes section for details.

  • The enable_unsupported_driver option will need to be set to True in the driver’s section in cinder.conf to continue to use the following three drivers.

    • Dell SC Series Storage Driver (iSCSI, FC)

    • Dell VNX Storage Driver (FC, iSCSI)

    • Dell XtremeIO Storage Driver (iSCSI, FC)

  • The following drivers have been marked as unsupported and are now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use these drivers.

    • Windows iSCSI Driver

    • Windows SMB Driver

  • Cinder now uses the RBD trash functionality to handle some volume deletions. Therefore, deployments must either a) enable scheduled RBD trash purging on the RBD backend or b) enable the Cinder RBD driver’s enable_deferred_deletion option to have Cinder purge the RBD trash. This adds the new configuration option ‘rbd_concurrent_flatten_operations’, which limits how many RBD flattens the driver will run simultaneously. This can be used to prevent flatten operations from consuming too much I/O capacity on the Ceph cluster. It defaults to 3.

Deprecation Notes

  • The following three drivers were marked unsupported. These drivers are deprecated and will be removed in a future release.

    • Dell SC Series Storage Driver (iSCSI, FC)

    • Dell VNX Storage Driver (FC, iSCSI)

    • Dell XtremeIO Storage Driver (iSCSI, FC)

  • Support for running Cinder in Windows operating systems has been deprecated because of the retirement of the Winstackers project.

  • The following drivers have been marked as unsupported and are now deprecated.

    • Windows iSCSI Driver

    • Windows SMB Driver

Bug Fixes

  • Bug #2008017: Hide value of the [coordination] backend_url option from logs because it can contain credential.

  • Bug #2016138: Handle missing volumes during cleanup of incomplete backups.

  • Infinidat driver bug #2017815: Fixed Infinidat driver to inherit compression setting by default for all newly created volumes. Admin can set True or False for the infinidat_use_compression option in the driver section of cinder.conf to explicitly enable or disable compression setting for all newly created volumes. Or leave this option unset (commented out) for all created volumes to inherit their compression setting from their parent pool at creation time. The default value is unset.

  • Dell PowerMax Driver Bug #2045230: Fixed the issue that Dell PowerMax SnapVx link fails as the linked device is not yet fully defined.

    Previously, the below operations could fail if the linked device was not yet fully defined at the time of the call. Now, when snapvx_unlink_symforce is enabled, those operations are not interrupted by not fully defined devices.

    By default, snapvx_unlink_symforce is False. Use extreme caution with this option. If used when a link is copy in progress or when a restore is restore in progress, this will cause an incomplete copy and data on the copy target would not be usable.

    Impacted operations:

    • Clone a volume

    • Create a volume from a snapshot

    • Create volume snapshots

    • Delete volume snapshots

    • Revert volume to snapshot

    • Create generic volume group from source

    • Unmanage volumes

  • PowerMax Driver bug #2051830: REST API calls to the PowerMax backend did not have a timeout set, which could result in Cinder waiting forever. This fix introduces two configuration options, rest_api_connect_timeout and rest_api_read_timeout, to control timeouts when connecting to the backend. The default value of each is 30 seconds.

  • PowerFlex Driver bug #2052995: REST API calls to the PowerFlex backend did not have a timeout set, which could result in cinder waiting forever. This fix introduces two configuration options, rest_api_connect_timeout and rest_api_read_timeout, to control timeouts when connecting to the backend. The default value of each is 30 seconds.

  • Dell PowerMax driver bug #2051828: The driver only recognised 10.0 as being Unisphere 10 and would try to use 9.2 for Unisphere 10.x (where x > 0), but now it correctly recognises 10.x as being Unisphere 10.

  • Bug #2045431: Fixed a data leak scenario where we preserve sparseness when reimaging the volume.

    We currently do a sparse copy when writing an image on the volume. This could be a potential data leak scenario where the zero blocks of the new image are not written on the existing volume and the data from the old image still exists on the volume. We fix the scenario by not doing sparse copy when reimaging the volume.

  • Bug #2036994: Fixed rollback of volume status if the reimage operation fails while checking image metadata.

  • Bug #1948962: Fixed operations that failed on volume types with 255 characters names (e.g. set quota limits or volume migrate).

  • Hitachi driver bug #2024418: Fixed to raise correct exception when volume is busy while performing delete volume operation.

  • HPE XP and NEC V driver bug #2012515: Fixed to use correct Host group name.

  • Hitachi driver bug #2011810: Fixed to use correct pool number for secondary storage on GAD environment.

  • HPE 3PAR driver Bug #2045411: Added support for ipv6 address in the 3PAR iSCSI driver.

  • HPE 3PAR driver bug #2021941: Fixed: Now clone of replicated volume can be created

  • HPE 3PAR driver Bug #2026718: Fixed: With this patch, added logic to fetch correct volume name on 3par (osv_name), rcg_name and vvset_name (for particular scenarios); so that volumes can be identified and deleted from 3par.

  • Bug #1988942: Increased size of volume image metadata values accepted by the Block Storage API. Volume image metadata values were limited to 255 characters but Glance allows up to 65535 bytes. This change does not affect the database tables which already allow up to 65535 bytes for image metadata values.

  • Dell EMC PowerMax driver bug #1980870: Fixed potential deadlock when moving volumes between Storage Groups.

  • Pure iSCSI & FC driver bug #2006960: Fixed attaching LUNs greater than 255. Driver leverages new os-brick functionality to specify LUN addressing mode.

  • [Pure Storage] Bug #2035404: Fixed issue with missing replication pod causing driver to fail on restart.

  • Pure Storage Cinder Driver: Fixed bug 2029005 to correctly disconnect a sync replicated volume from host on the secondary array when uniform option is set to True.

  • Bug #1952420: Fixed quota warnings about backups and backup_gigabytes when creating backups.

  • Bug #1969643: The RBD driver can now delete volumes with other volumes cloned from it (or its snapshots) in cases where deletion would previously fail. This uses the RBD trash functionality.

Other Notes

  • Nimble driver: Enable thin provisioning as default method while creating volumes.

  • Open-E JovianDSS driver: general rework of volume and snapshot creation and deletion.

  • Open-E JovianDSS driver: network interface selection on JovianDSS storage has been reworked.

  • [Pure Storage] user_agent string changed from reporting kernel version to operating system distro and version.