[release-announce] cinder 16.3.0 (ussuri)

no-reply at openstack.org no-reply at openstack.org
Thu Mar 11 10:39:08 UTC 2021


We eagerly announce the release of:

cinder 16.3.0: OpenStack Block Storage

This release is part of the ussuri stable release series.

The source is available from:

    https://opendev.org/openstack/cinder

Download the package from:

    https://tarballs.openstack.org/cinder/

Please report issues through:

    https://bugs.launchpad.net/cinder/+bugs

For more details, please see below.

16.3.0
^^^^^^


Upgrade Notes
*************

* This release contains a fix for Bug #1908315
  (https://bugs.launchpad.net/cinder/+bug/1908315), which changes the
  default value of the policy governing the Block Storage API action
  Reset group snapshot status (https://docs.openstack.org/api-ref
  /block-storage/v3/#reset-group-snapshot-status) to make the action
  administrator-only.  This policy was inadvertently changed to be
  admin-or-owner during the Queens development cycle.

  The policy is named "group:reset_group_snapshot_status".

  * If you have a custom value for this policy in your cinder policy
    configuration file, this change to the default value will not
    affect you.

  * If you have been aware of this regression and like the current
    (incorrect) behavior, you may add the following line to your
    cinder policy configuration file to restore that behavior:

       "group:reset_group_snapshot_status": "rule:admin_or_owner"

    This setting is *not recommended* by the Cinder project team, as
    it may allow end users to put a group snapshot into an invalid
    status with indeterminate consequences.

  For more information about the cinder policy configuration file, see
  the policy.yaml
  (https://docs.openstack.org/cinder/latest/configuration/block-
  storage/samples/policy.yaml.html) section of the Cinder
  Configuration Guide.


Bug Fixes
*********

* Bug #1888951 (https://bugs.launchpad.net/cinder/+bug/1888951):
  Fixed an issue with creating a backup from snapshot with NFS volume
  driver.

* IBM Spectrum Virtualize driver Bug #1890254
  (https://bugs.launchpad.net/cinder/+bug/1890254): Fix
  check_vdisk_fc_mappings is not deleting all flashcopy mappings while
  deleting source volume, when multiple clones and snapshots are
  created using common source volume.

* Bug #1890591 (https://bugs.launchpad.net/cinder/+bug/1890591): IBM
  Spectrum Virtualize Family: Fixed issue in do_setup of
  StorwizeSVCCommonDriver to save pool information in stats during
  initialisation.

* Bug #1908315 (https://bugs.launchpad.net/cinder/+bug/1908315):
  Corrected the default checkstring for the
  "group:reset_group_snapshot_status" policy to make it admin-only.
  This policy governs the Block Storage API action Reset group
  snapshot status (https://docs.openstack.org/api-ref/block-storage/v3
  /#reset-group-snapshot-status), which by default is supposed to be
  an adminstrator-only action.

* Bug 1913449 (https://bugs.launchpad.net/cinder/+bug/1913449): Fix
  RBD driver _update_volume_stats() failing when using Ceph Pacific
  python rados libraries.  This failed because we were passing a str
  instead of bytes to cluster.mon_command()

* Bug #1898587 (https://bugs.launchpad.net/cinder/+bug/1898587):
  Address cloning and api request timeout issues users may hit in
  certain environments, by allowing configuring timeout values for
  these operations through cinder configuration file.

* NetApp SolidFire driver Bug #1896112
  (https://bugs.launchpad.net/cinder/+bug/1896112): Fixes an issue
  that may duplicate volumes during creation, in case the SolidFire
  backend successfully processes a request and creates the volume, but
  fails to deliver the result back to the driver (the response is
  lost). When this scenario occurs, the SolidFire driver will retry
  the operation, which previously resulted in the creation of a
  duplicate volume. This fix adds the "sf_volume_create_timeout"
  configuration option (default value: 60 seconds) which specifies an
  additional length of time that the driver will wait for the volume
  to become active on the backend before raising an exception.

* NetApp SolidFire driver Bug #1891914
  (https://bugs.launchpad.net/cinder/+bug/1891914): Fix an error that
  might occur on cluster workload rebalancing or system upgrade, when
  an operation is made to a volume at the same time its connection is
  being moved to a secondary node.

Changes in cinder 16.2.1..16.3.0
--------------------------------

d73da7328 NetApp SolidFire: Fix duplicate volume when API response is lost
c469c1294 [SVF]:Fix clone fcmap not being deleted in cleanup
e50570b1d RBD: Pass bytes type for mon_command inbuf
71987b305 Log information about the Ceph v2 clone API
8426a5bdc [SVF]:Reduce slowness by caching pool information
f4359c523 Require oslo.serialization 3.1.2
f087536e4 NetApp SolidFire: Fix error on cluster workload rebalancing
4f40f059f RBD: Retry delete if VolumeIsBusy in _copy_image_to_volume
6c399a8b0 Correct group:reset_group_snapshot_status policy
5fecd1450 Fixed an issue with creating a backup from snapshot with NFS volume driver.
d00b1de8a Adjust requirements and lower-constraints
b790e81e7 NetApp SolidFire: Fix clone and request timeout issues


Diffstat (except docs and test files)
-------------------------------------

cinder/policies/group_snapshot_actions.py          |   2 +-
.../unit/volume/drivers/ibm/test_storwize_svc.py   | 222 ++++++++++++++++++++-
.../volume/drivers/solidfire/test_solidfire.py     |  22 +-
.../ibm/storwize_svc/storwize_svc_common.py        | 139 +++++++++++--
cinder/volume/drivers/rbd.py                       |  31 ++-
cinder/volume/drivers/remotefs.py                  |  10 +-
cinder/volume/drivers/solidfire.py                 | 136 +++++++++++--
lower-constraints.txt                              |  24 +--
...-backup-from-nfs-snapshot-2e06235eb318b852.yaml |   6 +
...s-not-deleting-in-cleanup-f5bbb467be1b889d.yaml |   8 +
...ion-is-not-saved-in-stats-22f302d941cd9fe2.yaml |   7 +
.../notes/bug-1908315-020fea3e244d49bb.yaml        |  38 ++++
.../notes/bug-1913449-4796b366ae7e871b.yaml        |   7 +
...nd-request-timeout-issues-56f7a7659c7ec775.yaml |   7 +
...icate-volume-request-lost-adefacda1298dc62.yaml |  14 ++
...or-on-cluster-rebalancing-515bf41104cd181a.yaml |   8 +
requirements.txt                                   |  12 +-
19 files changed, 692 insertions(+), 91 deletions(-)


Requirements updates
--------------------

diff --git a/requirements.txt b/requirements.txt
index 15907e5d6..a8797f50c 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -19 +19 @@ oslo.concurrency>=3.26.0 # Apache-2.0
-oslo.context>=2.19.2 # Apache-2.0
+oslo.context>=2.22.0 # Apache-2.0
@@ -28,2 +28,2 @@ oslo.rootwrap>=5.8.0 # Apache-2.0
-oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
-oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
+oslo.serialization>=3.1.2 # Apache-2.0
+oslo.service>=1.31.0 # Apache-2.0
@@ -44 +44 @@ python-swiftclient>=3.2.0 # Apache-2.0
-pytz>=2013.6 # MIT
+pytz>=2015.7 # MIT
@@ -59 +59 @@ os-brick>=3.0.3 # Apache-2.0
-os-win>=3.0.0 # Apache-2.0
+os-win>=4.1.0 # Apache-2.0
@@ -63 +63 @@ castellan>=0.16.0 # Apache-2.0
-cryptography>=2.1 # BSD/Apache-2.0
+cryptography>=2.1.4 # BSD/Apache-2.0






More information about the Release-announce mailing list