Current Series Release Notes¶
24.0.0.0rc1-71¶
New Features¶
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
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 parametertotal_volumes
(volumes already created in the RAID Group) and introducefragment_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 thetotal_volumes
parameter from the backend pool information when the type of backend pool is ThinProvisioning Pool.These two parameters can be utilised in future implementations of functions related to
filter_function
.This patch also enabled the
multiattach
in the driver information.
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.
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.
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
topy-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 toTrue
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 toTrue
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 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.
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 #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
isFalse
. 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
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 #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 #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 #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.
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.