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

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

= 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

Most likely needed to unblock the cinder gates.

Depends-On: https://review.opendev.org/676722
Change-Id: I9b59792008dd5bb003f1f3dbdd0403b1c679e4e2

Follow the same pattern of the other jobs which deploy devstack
but runs also functional tests (see devtack-tox-functional
and devstack-tox-functional-consumer).

Without this, the older branches where cinderlib functional tests
use Python 2 (stein, and soon train when that is branched) fails
because they try to install packages part of which are Python 3
only.

Change-Id: Ibd2862f30d4c451118fb96d1f56a09fd66b2d75a

Tests 1 and 2 (negative):
- Try to create an incremental backup from a backup
  previously created by another tenant (admin/user).

Test 3 (positive):
- Create backups as different tenants and confirm their
  incremental backups follow the respective parents.

Change-Id: I1d7896d9d7e20f7e6ac816af379f59cc86a3daa6
Depends-on: Icb621ff5966133f59d9d43ca2dd9f8e1919b1149

flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.

Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.

To avoid similar gate break in future, we need to bump the hacking min
version.

- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html

Change-Id: Ic84db0e885c6560120548ecb2ebc16dde1cd23d1

Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].

Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs

Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html

[1] https://opendev.org/openstack/tempest/src/commit/e8f1876aa6772077f85f380677b30251c2454505/.zuul.yaml#L646

Depends-On: https://review.opendev.org/#/c/727848/

Change-Id: Ic2d79795fa205525dc5adaaae342e0c6f29d28d9

This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7.3 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Remove install_command from tox.ini, the default is fine
- Switch to hacking 3.0, ignore W503 and W504 (as in cinder repo)
- Use TOX_CONSTRAINTS instead of obsolete UPPER_CONSTRAINTS

Change-Id: Ia623c8af7f03c25bce7e4600693a7e834ab70000

Non-voting for now.

Change-Id: Iea40482164ef1802330459cb8af5235c5acfae8a

According the support matrix, the revert feature is enabled
for the following backends
- LVM/iSCSI: on all supported stable releases
- RBD: since Ussuri.

As the execution time of the lvm-lio test is around
the default time limit and it easily times out,
bump it to 3 hours.

Change-Id: I3350a9efa295fd03f48be919e3dd13477f6adc7a

This patch adds a new gate job with tgt target configured.
This is the default target in cinder so it useful to have a gate
job with it.

Co-Authored-By: Rajat Dhasmana <rajatdhasmana@gmail.com>

Change-Id: I5c761de61f25975932d62aeb1270e2367d72c6e7

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

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

Depends-On: https://review.opendev.org/720213
Change-Id: Ic1fd6fcc9b9183f195c66f0022e913ae9734c97b

This patch adds the test to restore from an incremental backup.

Change-Id: I10272d737bbe3b196dfaf6ce242c8ccdf0787f5c

Currently backup service is disable in Ceph jobs.
In order to solve this cinder-tempest-plugin-cbak-ceph is
defined with the c-bak service enabled.

As a matter of fact the c-bak is redundant incase of lvm job
because the parent job already has enabled the service.

In addition, Tempest provides a blacklist file so that only
storage-relevant tests are executed. Use it instead of the
custom blacklist, which is removed in this patch.

This means that some tests which were previously skipped are
now executed.

If backup tests don't work with the LVM backend, they can be
disabled through the volume_feature_enabled.backup configuration
key.

Co-authored-by: Luigi Toscano <ltoscano@redhat.com>
Change-Id: Id809c37704d4ee741df4333ca01ddd4ec22f33b5

This patch standardizes the CONTRIBUTING.rst file.  This repo
has no docs, so this patch completes the goal for the
cinder-tempest-plugin.

Change-Id: I7b1d4f58e586653059dabe84ddde949a1f989b45

The changes should make this job a valid replacement for the legacy
cinder-tempest-dsvm-lvm-lio-barbican job defined inside cinder.git.

- rename as cinder-tempest-plugin-lvm-lio-barbican;
- add it to the gate queue as well, together with
  devstack-plugin-ceph-tempest-py3;
- use the proper functional tox environment provided by cinderlib;
- synchronize the blacklist with the one used by the legacy job,
  and use the same devstack options;
- remove barbicanclient and os-brick from required-projects,
  so that the stable libraries are used, as usual for normal jobs.
  Child jobs can add them if they need to test against
  the master version of those libraries.

And a few minor changes (namespaces for the repositories,
prepare it to be multinode-compatible).

Change-Id: I0ed43c8eda445af8da61d861536da1efdd5a7b1f

devstack-plugin-ceph-tempest job is py2 job and
not supposed to run on master gate. We need to use
its py3 version- devstack-plugin-ceph-tempest-py3

Change-Id: I1a817c8dc0d01292bdd89cd46caa094d1ecdad01

Change-Id: I3ff7a714d5fd61edd72e00c7a454c81724844f99
Closes-bug: #1853372

Remove the usage of api_version and let the library
code use catalog_type instead.
CONF.volume_feature_enabled.{api_v2,api_v3} have been deprecated
since rocky.

See also:
- https://review.opendev.org/#/c/698754/
- https://review.opendev.org/#/c/698757/
and other reviews.

Change-Id: Ic91f38ebff96df7d38a2d8cd2447e454c385c46c

Two changes to README.md are made:
1. Fixed command line for calling cinder-tempest-plugin tests using plugin name
2. Removed usage of deprecated tox command [all-plugin -> all].
https://github.com/openstack/tempest/blob/master/tox.ini#L55

Change-Id: Ic2c88acfba606592dd12677cc70649ff545c1222

Reference:
1. http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006478.html

Change-Id: Ie634a18c9684d89c799d383b6538941d048da8ae

1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Update some URLs to latest
3. Remove unncessary "=="

Change-Id: Iff24e8d5082d8ef8dc2d29ea92288bf418f5500d

Correct package name for Cinder Tempest plugin
is 'cinder-tempest-plugin'. It's used to upload package to
PyPI.

Change-Id: I6f35ec536031c02b9e6283311e25f7b78ee9c677

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.

This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.

This update should result in no functional change.

For more information see the thread at

 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html

Change-Id: If2b913e222ef0ed323c5700de677581d91238f02

This may help test the problem exposed in bug
1805790, but it will only trigger it if the job
is running with notifications turned on.

Related-Bug: #1805790

Change-Id: Ie1778624f51cfc05c5d42174065a21a6ceaae138

According to the revert to snapshot spec, it should not be
possible to revert a volume to a snapshot after the volume is
extended. This was fixed on [1] but the cinder_tempest_plugin
test still was being considering the old behavior.

[1] https://bugs.launchpad.net/cinder/+bug/1798503

Change-Id: I21d0b2291608922e46278ae5799478a5df0c4904