magnum-tempest-plugin 1.5.0 release

meta:version: 1.5.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: Ib91ae5f37dcbe96439011c71f1d445dd0ec6e719
meta:release:Code-Review+1: Ghanshyam <gmann@ghanshyammann.com>
meta:release:Code-Review+1: Spyros Trigazis <strigazi@gmail.com>
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>

magnum-tempest-plugin 1.4.0 release

meta:version: 1.4.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Commit: Martin Kopec <mkopec@redhat.com>
meta:release:Change-Id: I9f10b574dba8dc33221c2aec1cd9451137b19250
meta:release:Code-Review+1: Martin Kopec <mkopec@redhat.com>
meta:release:Code-Review+1: 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>

Since [1] is merged, quota in glance is enabled but limit is set to
1GB by default and this is too small for Magnum jobs using Fedora
images.
This change extends the limit to fix the issue caused by that low
limit.

[1] https://review.opendev.org/c/openstack/devstack/+/788056
Depends-on: https://review.opendev.org/802413

Change-Id: Id741fafc7e1da2d4e180f0745cd4d4b367472f06

magnum-tempest-plugin 1.3.0 release

meta:version: 1.3.0
meta:diff-start: -
meta:series: wallaby
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: I38346b9375d1d615081396ac55836bb17f9499bf
meta:release:Code-Review+1: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Code-Review+1: Spyros Trigazis <strigazi@gmail.com>
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>

magnum-tempest-plugin 1.2.0 release

meta:version: 1.2.0
meta:diff-start: -
meta:series: wallaby
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Commit: Ghanshyam <gmann@ghanshyammann.com>
meta:release:Change-Id: I3c4ad43a9e878ac4d749f8a96c36a3da24d121e9
meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com>
meta:release:Code-Review+1: Spyros Trigazis <strigazi@gmail.com>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>

Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex

old name are still supported for compatiblity but we recommend
to switch to new one.

Depends-On: https://review.opendev.org/c/openstack/tempest/+/774835
Change-Id: I5d66e18757d516f8c761875bd2f824d0e839f1ac

Depends-On: https://review.opendev.org/c/openstack/magnum/+/774142
Change-Id: I6baad8e3bf640959ee9e34b8e5fdef1a0bf9295b

Cluster creation fails on the CI due to an issue similar to what we've
seen before for another test (test_create_list_sign_delete_clusters).
Disable it for now.

story: 2007272
task: 38867

story: 2007851
task: 41443

Change-Id: Ie91fdfe71058b45c5fd1217920b8b5b993e47734

magnum-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: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Commit: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Change-Id: I6b8d781c14797a7a79a51c72e2cd7a4c7b556f19
meta:release:Code-Review+1: Feilong Wang <flwang@catalyst.net.nz>
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>

keeping magnum-tempest-plugin-tests-api job running on bionic nodeset till
https://storyboard.openstack.org/#!/story/2007732 is fixed
otherwise base devstack jobs switching to Focal will block
the gate.

Story: #2007865
Task: #40190

Change-Id: I78c8f92428efd27d604258f361077d909a27aa23

This is kind of a race condition issue, Tempest is doing a wait and check
when it is trying to delete a cluster. However, at the very end of the cluster
deletion process, a cluster GET request may get a HTTP 400 error which
will cause the Tempest case failed. This HTTP 400 exception reported
by a cluster GET request should be caught and take cluster as still existing.

Task: 40120
Story: 2007833

Change-Id: Ic97abf8d4d584f35b18bff9eab5d3e5ac80c0f02

The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I17c818e0e2cb5b4dc2b24cf689ceeb9b391c83bf

Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems

Update Sphinx version as well.

Disable openstackdocs_auto_name to use 'project' variable as name.

Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.

openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.

See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html

Change-Id: I54eee940d3c787fddc1278619981d7a90310fbd0

Change-Id: Iaf0b95597d6dc968c9745690f4a2663de8442876

We don't need this in a Python 3-only world.

Change-Id: I0ec4a2fe359c285460f64949943649b25938f3b1

Update docs building, cleanup a bit:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
  python 3, create doc/requirements.txt
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.
* Move constraints into deps, use TOX_CONSTRAINTS instead of
  obsolete UPPER_CONSTRAINTS
* Update to hacking 3.0, fix problems found

Change-Id: I76fe5602928bede439133993b0d85669228f25ed

--

Bump the openstackdocstheme extension to 1.20

Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.

Ic9207bb8d3e602dd71cc4c7cefde739130f3d48b

--

Blacklist sphinx 2.1.0 (autodoc bug)

See https://github.com/sphinx-doc/sphinx/issues/6440 for upstream details

Ia029f66cfde96d97754e38b5278f1b24081a09e0

--

tox: Keeping going with docs

1. Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.

2. Remove the py27 from tox since magnum already drop support python 2.7

[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045

I6e713b51cf9fac87e696fdfce8156f656a0f1df5

--

Change-Id: I53800a688fae3ba9cc551b0ceffe96938f2df59d

This commit defines magnum-tempest-plugin-tests-api job which uses the
new devstack-tempest as parent job recommended for running
Tempest tests in Zuul v3.

Story: 2007561
Task: 39470

Depends-on: https://review.opendev.org/#/c/721265

Change-Id: If7b77099a90d405e248c80777fa5e8b3612b5c2e

Story: 2007561
Task: 39512

Change-Id: I2a5ba0a3bbc99c31af5de96e5b2acfa6107b698e

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

magnum-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://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Change-Id: I58baf3f7361468de98fc43a1aed036af9c4e5051