cinder-tempest-plugin 1.4.0 release

meta:version: 1.4.0
meta:diff-start: -
meta:series: wallaby
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Luigi Toscano <ltoscano@redhat.com>
meta:release:Commit: Luigi Toscano <ltoscano@redhat.com>
meta:release:Change-Id: Ib6efac12278c12aa1f320c12a86cbcd164faed90
meta:release:Code-Review+1: Brian Rosmaita <rosmaita.fossdev@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:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>

Change I0b6ab9fb943c7b0925a0a0d2490a8bcdfa76cedc removed the 'member'
user from the default roles assigned to dynamic tempest users.
This broke cinder-backup with the default swift backend.

Set the full list of roles, including 'creator' which should be
added by the barbican devstack plugin. Unfortunately the values
here overrides any other setting.

Change-Id: Id6dc96915f5b15827e6e8f58cc8195a0f76e9686

While waiting for tempest scenario manager to stabilize its API,
a copy of it has been imported, so make sure to use it and to not
rely on tempest's one (whose API is changing during the stabilization
process, so it may break anytime).

Just one file needs to change its imports.
At the same time, fix the import order for another file.

Change-Id: I29c4784d59151948778cad57b7db56a368ed821d

Each test should have one:
https://opendev.org/openstack/tempest/src/tag/26.0.0/HACKING.rst

Change-Id: Icd119d710376c0f5e4c6d2932ca39d55648cc9b7

We don't really have unit tests in the repository and any py3x venv
would not really be useful (the tests are executed through tempest),
but let's remove the old dependency anyway and depend on stestr
like all the other OpenStack projects.

Change-Id: I52d06f1c1e141cb455fb7a823a27be532afb4c16

This patch adds data integrity tests for snapshot with the following
procedure :

1) create a volume from image
2) Boot an instance from the volume
3) create file on vm and write data into it
4) create first snapshot
5) repeat 3
5) create second snapshot
6) repeat 3
7) create third snapshot

Now restore the snapshots one by one into volume, create instances
from it and check the number of files and file content at each
point snapshot was created.

We are also temporarily making a copy of tempest scenario manager until
the actual manager is available for import in tempest plugins.

Change-Id: I5c5ff6f996dd39b52fada82f3938b628e58b0a2c

It doesn't seem to provide any benefit and is also removed from cinder
project.
For detailed reason, please look into the commit message of the cinder
patch[1].

[1] https://opendev.org/openstack/cinder/commit/b0a56ddd252670dadb2c5e3eb0b03bfc7f93623d

Change-Id: I9a7749288706c8b326c1acd0cef6edd5ea91503e

An independent image isn't required for these tests and additionally
isn't required when calling create_server as the lack of an image
results in CONF.compute.image_ref being used by
tempest.common.compute.create_test_server [1].

The creation of this image resulted in the nova-ceph-multistore job
breaking as documented in bug #1912607. This broke as we use the job to
provide both our core ceph coverage and slightly more edgey topologies
using Glance multistore and the [workarounds]/ workaround option. This
option blocking the download of rbd images via g-api when n-cpu can't
clone the rbd volumes directly, as caused by the image creation in
test_volume_encrypted.

Iaf6f6e0dbcb25561bf00e969e1964cd30e974e64 is currently skipping any
encryption test in the nova-ceph-multistore job to workaround bug
 #1912607 for the time being but we would obviously like to revert that
if possible and expand our coverage.

A follow up change will also propose adding nova-ceph-multistore to the
gate of this plugin to avoid future breakage.

Related-Bug: #1912607

[1] https://opendev.org/openstack/tempest/src/branch/master/tempest/common/compute.py#L108-L109

Change-Id: I50d3b874b7e0676436c434be6c059f221041560f

Due to an error in the _setup_encryption_keys volume rekey code, a
cloned encrypted volume that has been rekeyed will specify an
encryption key different from the key used to format the volume,
so it cannot be attached.

This test scenario will cover this feature and also the case of
source-vol feature.

Related-Bug: #1904440
Depends-on: https://review.opendev.org/#/c/762884/
Change-Id: I846b96ef925c34162cf462da91d854ceacabe022

So that changes to this plugin (at least, most of them) don't break
victoria.

As stein moved to EM, remove its job according the common guidelines.

Change-Id: If4857a8beaa46b48c0f7d44ff707dd44425b530c

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removed specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug however it doesn't
produce any doc or releasenotes, but uniformization can't hurt and help
us in the future.

/!\/!\/!\
Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.
/!\/!\/!\

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Change-Id: I166c9479d94a42114adc94778140a9878a5949c5

Change-Id: Ie7e6b07dad5d2d732eac809e14714ccb19850bba

The test cases should wait for CG to be available first before moving to
create volume in the CG.

Change-Id: Iac0aefff7a2277e1d3a36d8943e285a226a6830f
Closes-Bug: #1897532

This is fixed by https://review.opendev.org/#/c/753699/4
SO removing the TODO to anable to run the job on ubuntu focal.

Change-Id: Idce913345c1bf8a47e678d706364c09837221a82

cinder-tempest-plugin 1.2.0 release

meta:version: 1.2.0
meta:diff-start: -
meta:series: victoria
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Commit: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Change-Id: I886b9ea80b6e042947caf1d4f9765201bcbe4643
meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com>
meta:release:Code-Review+2: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Workflow+1: Sean McGinnis <sean.mcginnis@gmail.com>

As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).

Most of the Tempest jobs will be migrate automatically once devstack
base job start running on Focal[2].

Stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.

Keeping barbican jobs running on bionic nodeset till
https://storyboard.openstack.org/#!/story/2007732 is fixed.

[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
[2] https://review.opendev.org/#/c/734700/

Story: #2007865
Task: #40179

Change-Id: Ief046344957004a5ad29337864ace5837d6c553d

cinder-tempest-plugin 1.1.0 release

meta:version: 1.1.0
meta:diff-start: -
meta:series: victoria
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Brian Rosmaita <rosmaita.fossdev@gmail.com>
meta:release:Commit: Brian Rosmaita <rosmaita.fossdev@gmail.com>
meta:release:Change-Id: If7aa154745235ab13a55585a096f29a62ca5c35c
meta:release:Code-Review+2: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com>
meta:release:Workflow+1: Hervé Beraud <hberaud@redhat.com>

= Fix the imports of shared exceptions =

Shared tempest exceptions (like TimeoutException) are defined
in and exported by tempest.lib, so use them correctly.

= Directly define the exceptions used by this tempest plugin =

While those exceptions have been defined in tempest.lib through
I62e0ba556b884c94f6e8796a2e6f6d8083277fa4,
they really belongs to this plugin only, so define them here.
Other tempest plugins followed the same pattern.
Moreover, the current import would need to be fixed anyway,
because it should import the exceptions from tempest.lib.exceptions
instead of tempest.exceptions.

Closes-Bug: #1858417
Closes-Bug: #1889537
Change-Id: Ie54c2a1dc25b647a0f0d10bcad6ba62023986741

When a volume is created from an image with a cinder_img_volume_type
image property, and a volume_type is not specified in the volume-
create call, the resulting volume should be the specified volume_type,
not the default type.

Change-Id: If8edd24ba5183522ebe8202bbf6b62b41b3febe9

The functional tests are executed from the tempest node(s), which means
that the collection must happen from the same place, not all nodes;
otherwise the playbook code fails on pure compute nodes.

Change-Id: Ibe1796e1380add34b6d8f19606bb55fda13c3c08