2024.2 Series Release Notes

25.0.0-6

Bug Fixes

  • Fixed the volume property signature_verified propagating to images created from volumes. That property could later conflict with the same property being added again when creating a new volume from such image, preventing the volume from being created successfully. This volume property is created whenever a volume is created from an image for the purpose of indicating that the image signature was verified on creation, and was not intended to be propagated further if a new image is created from such volume.

  • Bug #2083532: [Pure Storage] Fixed creation of volumes with only IOPS qos.

  • Bug #2065713: Due to incorrect exception handling, ImageNotFound errors in the RBD driver’s get_manageable_volumes operation would propagate up to the API layer rather than being caught and handled in the driver.

25.0.0

New Features

  • Dell PowerStore driver: Enabled cinder volume active/active support. This allows users to configure Dell PowerStore backends in cinder clustered environments.

  • Dell PowerStore Driver: Added QoS (Quality of Service) support for PowerStore 4.0 or later versions.

  • Add the clone_across_pools driver capability Drivers can now declare that they can clone a volume into a different pool. Essentially, if this capability is declared, Cinder will skip the check that the pool of the destination volume is the same as the pool of the source volume. Some drivers do not have such a restriction and it may be possible to complete the “create volume from image” operation very efficiently instead of falling back to the “attach and dd” option. This affects creating a volume from an image with and without the image cache. For more details please check bp clone_across_pools

  • NetApp ONTAP ISCSI/FC drivers: Enabled support for Active/Active environments in the NetApp ISCSI/FC drivers (including replication).

  • Fujitsu Eternus DX driver: Added cli operations when creating snapshot

    Fujitsu Eternus DX driver used to create snapshot using SMI-S, resulting in the inability to extend the source volume.

    To make the volume extendable after creating a snapshot, an additional parameter fujitsu_use_cli_copy is introduced with a default value of False.

    • If fujitsu_use_cli_copy is set to False, create a snapshot using the conventional SMI-S method.

    • If fujitsu_use_cli_copy is set to True, create a snapshot using the CLI method, allowing volume extension of the source volume.

    Note that fujitsu_use_cli_copy cannot be set to True when the type of target pool is RAID Group.

    See the Fujitsu ETERNUS DX driver documentation for details.

  • Fujitsu ETERNUS DX driver: Add metadata to snapshot

    After the snapshot is created, upload the information of the snapshot on the storage to the metadata.

    The metadata has the following information:

    • FJ_SDV_Name

    • FJ_SDV_No

    • FJ_Pool_Name

  • Fujitsu ETERNUS DX driver: Improve volume deletion

    To improve the volume deletion process, add a step to check associated copy sessions. Additionally, it also improves the process of retrieving storage-managed volume numbers.

    There was a problem where the volume could not be deleted because the copy session information acquired by SMI-S IF from ETERNUS DX Storage, which was cached and did not reflect the information that had just been executed.

    This problem has been addressed through improvements in information retrieval.

  • Fujitsu ETERNUS DX driver: Add fragment capacity information of RAID Group.

    ETERNUS DX driver have two types of storage pools: RAID Group and ThinProvisioning Pool. Volumes can not be created in RAID Groups for the following situations:

    • The maximum sequential physical free space is smaller than the volumes to be created.

    • 128 volumes have already been created in the RAID Group.

    For the above reasons, to monitor the maximum sequential physical free space and total volumes in the RAID Group, when updating pool information using Get Volume Stats, also update parameter total_volumes (volumes already created in the RAID Group) and introduce fragment_capacity_mb (maximum sequential physical capacity) to the backend pool information if the backend pool is a RAID Group.

    Meanwhile, since creating volumes on ThinProvisioning Pool does not encounter the above restrictions, parameter fragment_capacity_mb will not be added into the information, and remove the total_volumes parameter from the backend pool information when the type of backend pool is ThinProvisioning Pool.

    These two parameters can be utilized in future implementations of functions related to filter_function.

    This patch also enabled the multiattach in the driver information.

  • Fujitsu Eternus DX driver: Added support for revert to snapshot operation.

    Added support of revert to snapshot functionality.

    If a volume with snapshots has been extended, causing a mismatch in size between the origin volume and the snapshot, reverting will be guarded by cinder-api.

  • Fujitsu ETERNUS DX driver: Added support for update migrated volume

    Now we update the required values to successfully complete the migration.

    See the Fujitsu ETERNUS DX driver documentation for details.

  • Hitachi driver: Added QoS support.

  • Lightbits driver: Added support to create multiple snapshots from the same volume simultaneously when using the Lightbits cinder driver. Under certain conditions, older releases of the Lightbits api-service will return various status codes (including HTTP status codes 500 and 503) that could indicate transient failures. Added retry logic on such errors becuase there’s a good chance that the error is transient and subsequent calls will succeed.

  • Lightbits driver: Added a new configuration option lightos_use_ipacl, defaulting to true. When set to true, the Cinder driver will restrict access to each volume to the IP addresses of the host machine that the volume is attached to.

  • HPE Nimble driver: Added group replication support.

  • Pure Storage FlashArray drivers upgraded to remove REST 1.x support and changed to REST 2.4 as the minimum supported version.

  • Pure Storage FlashArray drivers changed minimum supported Purity//FA version to 6.1.0.

  • The StorPool driver now declares the “clone across pools” capability, which allows it to create a volume into an arbitrary StorPool-backed volume type from a StorPool-backed Glance image.

  • StorPool driver: improved the way volumes are cloned into different StorPool templates (exposed as Cinder storage pools) if requested, eliminating some data duplication in the underlying StorPool cluster.

  • StorPool driver: implemented revert to snapshot, which happens immediately i.e. without deleting and recreating the volume.

  • 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.

Upgrade Notes

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

  • [Pure Storage] Changed Python SDK driver requirement from purestorage to py-pure-client to support change to Purity//FA REST 2.x API calls.

  • The Quobyte driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it.

Deprecation Notes

  • The GlusterFS backup driver has been deprecated. It will be removed in the 2025.1 release.

  • The Quobyte driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it. As an unsupported driver, it is eligible for removal from the cinder code base if its third party CI system is not fixed.

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 previous 2023.1 version, the live migration fails without a pool name. This update add the ability of live migration without a pool name.

  • StorPool driver bug #1939241: Fixed the creation of encrypted StorPool volumes by dropping the needlessly and incompletely overridden _attach_volume() and _detach_volume() methods.

  • Bug #1946483: Fixed an issue where admin user fails to delete backup of an encrypted volume with an oslo_config.cfg.NoSuchOptError error in logs of cinder-backup service. With this fix cloud admin is able to delete backups of encrypted volumes created by other users if Barbican API policies allow it.

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

  • 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

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

  • 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 #2077643: Fixed “cinder-manage quota sync” CLI command, which failed with an sqlalchemy error when a project id was not specified.

  • Bug #1938488: When cleaning up a failed backup, clean up the snapshot status when the backup source is a snapshot

  • StorPool driver bug #2002995: When retyping a volume on a StorPool backend to a different volume type also on that StorPool backend but using a different StorPool template, occasionally the retype operation would fail or the old volume could be left attached to a StorPool client. This issue has been fixed in this release.

  • 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.

  • 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 psuedo REST API server

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

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

  • HPE 3PAR driver bug #2044255: Fixed: In peer persistence setup, when volume is attached to instance, now LUN ids are returned from both the arrays.

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

Other Notes

  • Enabled Guru Meditation Reports on Cinder wsgi. When running Cinder under WSGI, we might want to have Guru Meditation Reports as well as when running outside of WSGI.