cinder 20.0.1 release

meta:version: 20.0.1
meta:diff-start: -
meta:series: yoga
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Jon Bernard <jobernar@redhat.com>
meta:release:Commit: Jon Bernard <jobernar@redhat.com>
meta:release:Change-Id: I39dce8bc94c66051ecef94b0177d367c85aab05c
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>

In multi host environment, if volume is attached to instances present
on different hosts, detach operation works partially.
As a result, at later time the volume cannot be deleted.

Details are explained in launchpad bug.

This patch performs following:
During detach volume from instance, both possibilities are considered:
the instances can reside:
[1] either on same host.
[2] or on different hosts.

case [1]:
In such case, behaviour is same as earlier i.e vlun is not deleted
upon each detach operation i.e skip remainder of terminate volume
connection. The vluns are deleted only on last detach operation.

case [2]:
In such case, vlun of that host on 3par array is deleted separately
upon each detach operation.

Closes-Bug: #1958122
Change-Id: I47e8e86a495802a21570e23ecf7428fccc8b3d60
(cherry picked from commit 3ed2f38e)

We're supposed to fail an import request for an already existing
backup, but the current code confuses an existing backup record with
one we created for the import, and during quota rollback, will
destroy either one.  Simplify the logic so that we check whether
there's an already existing backup first and bail without even
bothering to make an unnecessary reservation, hence leaving us nothing
to roll back or delete by mistake.

Also revise and add tests.

Closes-bug: #1965847
Change-Id: I3c0e365f5dc3c32975343f538c6029f02ac7c2b5
(cherry picked from commit 6386cbb0)

The SVM account has no access to the node name and it cannot create
the QoS policy, so the QoS min support can be dropped.

Includes the release note formatting fix from change I6544e5d68714.

Closes-Bug: #1924798
Change-Id: I216f84ed379d4554d5d9adee31f9af6f4d54ea94
(cherry picked from commit b7466f54)

A temporary volume can be deleted while it is in use by DELETE API
accidentally because its status is `available`. To avoid this deletion,
this fix sets a value which doesn't accept deletion to volume status of
a temporary volume. When a temporary volume is used for backing up,
`backing-up` is set. When a temporary volume is used for reverting a
snapshot, `in-use` is set because the volume is attached by a host.

Closes-Bug: #1970768
Change-Id: Ib6a2e4d68e532b91161df5245c17ce815f12f935
(cherry picked from commit 53c13891)

Before this change, the errors from tempest run are suppressed
in order to always execute cinderlib tests.

Use the variable exported by run-tempest instead,
and fail properly if needed.

This is a port of Ic1fd6fcc9b9183f195c66f0022e913ae9734c97b
from cinder-tempest-plugin.git to this repository.

Change-Id: I216a82a29c7fb6b1b2fac95b2a1af667c4e2b22d
(cherry picked from commit 7e04b5b0)

[Spectrum Virtualize family] While retyping GM to GM or MM to MM or
GMCV to GMCV, chfcmap() call is being made which is resulting in retype
operation failure.
Error: CMMVC7154E The task cannot be completed because the specified
FlashCopy mapping is controlled by a Metro Mirror or Global Mirror
relationship.

chfcmap() should not be called for any FC map which is rc_controlled.
Hence while retyping global mirror to global mirror or
metro mirror to metro mirror or GMCV to GMCV volume, this error comes
up as the FC map of the volume is rc_controlled for these replication
volume-types.

Closes-Bug: #1968159
Change-Id: Ic97a2501b4c895b2b655284bcc320036c2d4e217
(cherry picked from commit b99e73e9)

Closes-Bug: #1929223

Change-Id: Iaaac11faf545db15e0b3161331a863068d50d199
(cherry picked from commit daf77efa)

cinder 20.0.0 release

meta:version: 20.0.0
meta:diff-start: 19.0.0.0rc1
meta:series: yoga
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Előd Illés <elod.illes@est.tech>
meta:release:Commit: Előd Illés <elod.illes@est.tech>
meta:release:Change-Id: I3516aa1f6a236f4415f3e1c3373059b73efa2c04
meta:release:Code-Review+1: Goutham Pacha Ravi <gouthampravi@gmail.com>
meta:release:Code-Review+1: Matthias Runge <mrunge@redhat.com>
meta:release:Code-Review+1: Ghanshyam <gmann@ghanshyammann.com>
meta:release:Code-Review+1: wu.chunyang <wuchunyang@yovole.com>
meta:release:Code-Review+1: zhurong <aaronzhu1121@gmail.com>
meta:release:Code-Review+1: Rajat Dhasmana <rajatdhasmana@gmail.com>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Workflow+1: Elod Illes <elod.illes@est.tech>

This change is being made directly to stable/yoga because
the matrix is currently under revision in master (Zed
development) and is much different there.

Change-Id: Ib616995b987e695839461f20387bafc114cdb04b

Change-Id: I7fad82b7e123f9153eb15637fbb3ca5db0be8d27

Change-Id: I2e7c04b12d1a1ef99b253ae8dbf47faa290ad1bf

Managing a volume to an encrypted volume type should not be allowed.
One reason is that there is no way for an operator to specify an
encryption key ID for the volume. Another is that we already don't
allow a volume of an encrypted type to be un-managed, so this change
will be symmetric.

Also update and correct the api-ref for this call.

Co-authored-by: xuan <xuanyd@outlook.com>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>

Change-Id: Ic2da41f3962c1108f974aca952bce3da6d6ac277
Closes-bug: #1944577
(cherry picked from commit 8088dc95)
change:
  cinder/tests/unit/api/contrib/test_volume_manage.py - used a
  feature of unittest.mock that was introduced in py38; rewritten to
  be compatible with py36

cinder 20.0.0.0rc1 release candidate

meta:version: 20.0.0.0rc1
meta:diff-start: -
meta:series: yoga
meta:release-type: release candidate
meta:pypi: no
meta:first: no
meta:release:Author: Elod Illes <elod.illes@est.tech>
meta:release:Commit: Brian Rosmaita <rosmaita.fossdev@gmail.com>
meta:release:Change-Id: I6543949d5c6636b316330e5b7e17be5708bca174
meta:release:Code-Review+1: Rajat Dhasmana <rajatdhasmana@gmail.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/yoga branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Ic1e7f19172524a31e12426f61b6a2c2b5cbafa37

Change-Id: I9f9fdaf49fae87b40f1c7a5608bb352cc5c44e21

Also update the max microversion for yoga in the api version
history document.

Change-Id: I0573499b6d4141d3739033d3af5dbfec681fa908

the compression value in get_volume_stats should be ["True", "False"]
and not dependent on the
configuration: "lightos_default_compression_enabled"
if the flag is false, we can not create volume type with
compression=True. the backend is filtered in the scheduler.

Closes-Bug: #1962221

Signed-off-by: Yuval Brave <yuval@lightbitslabs.com>
Change-Id: I09fe872eca1b112f67bad7297de5893696f83373