We have stable/victoria, stable/wallaby, and
stable/victoria released so we should add their job on
master gate to keep branchless tempest plugins compatible
to those branch.

This also removes the stable/train|stein job as thare are in EM
state now.

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

Change-Id: I9440ed27823193054fdd3e0a4ff7785fadca8d24

Change-Id: I510052c54562760d5da35f8b8e8b4a8a04baece7

Change-Id: Ieb3a27f5bcf8885ab0a8c2fb9e1d5f7e9a39a9bc

Change-Id: I7d51a4e6092d22ce7e3d46054a6d90cb7d362bec

Change-Id: I07c3788161dbb922efca50daa808fdcd703c73f6

Change-Id: I45e3dfbd30ee6236222c8bd8a462cd060cbddd72

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removing 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.

/!\/!\/!\
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: If0c66938ff1b505aba53d17293ff70612a3bd889

* Replace .testr.conf by .stestr.conf for migration and update
  .gitignore and test-requirements.txt file accordingly
* Use py3 as the default runtime for tox
* The patch bumps min version of tox to 3.18.0 python in order to
  replace tox's whitelist_externals by allowlist_externals option
* Updated ostestr occurances to stestr`

Change-Id: Iacc4e5054deb6ef832085d131c933e48e418bf1b

Change-Id: Id518fe93f5b17b5809db5f385f270da0e2722372

update receiver, the receiver not found; update receiver no param

Change-Id: I442cb24292d3be05260a4b3621262bc90886d943

Change-Id: Ia5606fae47ee30646e3a1cfd98d16da524d66a64

negative cases for update action, action id not exist, invalid status

Change-Id: I74b552e57508611546bd39692dfa7164aa49ee3e

- six.moves.BaseHTTPServer
- six.moves.http_client

Change-Id: I855d13af3f1f5ffb3543b864655624c99dbce403

api for list profile type operation

Change-Id: Ic1e76edf56cad602b18baf4f3380d8b89010c976

Convert all code to not require six library and instead
use python 3.x logic.

Change-Id: I0f7d623d58072bc3b7761a3c70832298cbc00de1

This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Use newer openstackdocstheme and Sphinx versions
- Remove install_command from tox.ini, the default is fine;
  move constraints into deps
- Remove Babel from requirements, it's not needed for running;
  remove babel.cfg likewise
- Use TOX_CONSTRAINTS_FILE, UPPER_CONSTRAINTS_FILE is obsolete
- update hacking to version 3.0

Change-Id: Ibcb7be4fd057b24147b7b562302ea362ad8c71b3

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

Change-Id: I31798ce47063a55e6ef29d713dc156c2d873e3cb

OpenStack is dropping the py2.7 support in ussuri cycle.

senlin-tempest-plugin is ready with python 3 and ok to drop the
python 2.7 support.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal - https://review.opendev.org/#/c/691178/

Change-Id: I53e47c4cf7446c38eb47ad1c889483197a3d8698

Retrieve max api version at client creation and skip tests that require
higher api versions than supported.

Change-Id: I1d099157966bc73e6d104f7d293f4a0e30180662

This was hiding a bug with flavor_id. Make sure we
delete the cluster so that it will always fail gracefully.

In addition we also stop re-using the same private network
for cluster tests and instead create custom networks to
prevent race conditions between tests.

* Add a small retry for logic for deleting subnets and networks.
* Add override to network name to allow for randomized names.

Change-Id: Ibcf1b25bc6e5e3a54678646a397dc1c41b1d29af

- Added API tests for nodes returning tainted fields in v1.13+
- Fixed missing and duplicate idempotent ids.

Depends-On: https://review.opendev.org/#/c/689606/
Change-Id: I283467b3dc4a6f32b1c7b81c2e97a52d8c0c9f1e

There is no garuantee that content-length is set when
the payload is empty. It is also not a required field for
HTTP Status 204 (No Content) or DELETE.

Change-Id: Ifdd7cdef3a214a1153563c12e349dda9f179a2ad

Introduced a new configuration variable to set the
supported health policy version that is used to
help determine if we can run the health related
tests.

Change-Id: I025aada17db6900d3e4328d5c09890e4f260f4d6

Change-Id: Iee5f537677098e1db0e42b86c21833472bdea9de