Current Series Release Notes

26.0.0.0rc1-37

New Features

  • Cinder now supports setting-up cgroups with the cgroups v2 API, which is used when doing migration of block device with the LVM backend.

Bug Fixes

  • IBM Spectrum Virtualize Family driver: Bug #2003300: Enable support for mirror-pool option for metro-mirror replication and global-mirror replication volume-types.

  • Bug #2082587: Fixed backup restoration throwing TypeError on new volume.

  • Bug #2105961: Fixed issue in NVMe-oF target driver to validate the nqn property (NVMe-oF) instead of the initiator property (iSCSI) in the connector which caused attachment failures in non-iSCSI environments.

  • Bug #2111461: Fixed issue preventing cinder-manage command to purge deleted rows due to foreign key constraint errors. This happened as timestamp for bulk delete operations were recalculated per table resulting in slighty different intervals for deleting rows on primary and dependents tables.

  • Bug #2107451: Fixed crash of cinder-manage quota sync if there is a row in the quota_usage table with the value groups for column resource

  • NFS driver bug #2074377: Fixed regression caused by change I65857288b797 (the mitigation for CVE-2024-32498) that was preventing the creation of a new volume from the second and subsequent snapshots of an existing volume.

  • RBD driver bug #2092534: Fixed uploading a volume to image when image has different format than volume.

  • Bug #2062539: Fixed reimage operation when the image is backed by a volume snapshot.

  • HPE 3par driver bug #2112433: Fixed failure observed when vlan ip is same as iSCSI ip by ignoring the duplicate ip

  • Pure Storage driver bug #2100547: Fixed issue where volumes created as clones from a source image volume did not get the defined QoS settings associated with the volume type used.

  • Pure Storage bug #2101859: Fixed issue where LACP bonds were not been correctly identified as iSCSI and NVMe targets.

  • Bug #1886543: On retypes requiring a migration, try to use the driver assisted mechanism when moving from one backend to another when we know it’s safe from the volume type perspective.