We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ie0a39407a98875afc7d2d87663b4a17c27fa8fc7
Supported stable branches in maintenance state
(ussuri, victoria, wallaby, and xena) 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] e8f1876aa6/.zuul.yaml (L646)
Change-Id: Ib7b44634eae3b3ee4040380f589b1964a783f99b
Since oslo.context=4.0.0 Feb 3, 2022 the deprecated argument
tenant was removed [1]
[1] f4cbe4c296
Change-Id: I710a19e14c795b4c74b7a772fbd80809c9777639
The default nodeset was just changed to focal [1], which in the absence
of the python-is-python3 package doesn't provide a python binary.
[1] https://review.opendev.org/c/opendev/base-jobs/+/789098
Change-Id: I55924ec1721181f8301357729df5d2c4abcad892
Adds basic support for configuring various parts of the tests to
make it easier to use them in environments which are configured
differently to DevStack. Specifically in this case the motivation
is to run the Monasca Tempest tests in Kolla CI.
This should be a NOOP change for existing environments.
Change-Id: If6be3a4d54a7b10c3ff40f9ed34045c50ffc3bae
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.
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: I5ebcd8f2cfa9f44830279679e3d6bcd24212bd93
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: Iea7d54b523130f0e3b251db0bacd3421ec7f99f6
Update docs building:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
python 3
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.
Change-Id: I5678058e43df7e708c7aefd7c06431ab21415e34
By allowing all notification types to support periodic notifications
these tests are no longer required. After this feature has been merged,
some tests could be added back to prevent regressions in the new
behaviour.
Depends-On: https://review.opendev.org/719989
Change-Id: I18a27800b8c1b28ab224375b42c57ac6a0f7ae78
Story: 2006837
Task: 37421
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found by updated hacking version.
The tempest plugin is used on older branches as well.
We really only need hacking on master anyways,
where we no longer support python 2, so here we
make the requirement specific to python 3.
Change-Id: I39f95e4ce193c1435c4901825bed949cdaaba72e
We should run the job testing the new merged API.
The change also removes Pyhon 2 tempest tests which are not supported
anymore.
Additionally, temporarily set the job as non-voting to allow merging
cross-dependant changes in API and tempest test related to ELK upgrade.
Change-Id: I4e679ca48a971bf39231688b57d03fc0ccd48183
Story: 2003881
Task: 37984
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: I5d405167c73b6e2409d6673e116475c67b18b96e
At present, dimensions are not scoped by time window, which makes
dimension related queries to large databases timeout because it searches
all of time instead of a time window specified on the grafana app.
This commit adds tempest tests to accompany the changes to the API
server and as such, depends on it.
Depends-On: https://review.opendev.org/#/c/670318/
Change-Id: Ibc5378deea51a18ed7dac857b26d770950b17620
Story: 2006204
Task: 35805
The change unifies the usage of text string literals in the package and
declares them as unicode. It simplifies comparing test values with
actual results across Python 2 and 3 deployments. It also fixes the bug
described in the user story.
Change-Id: I87c38faf41f7c1bff72d45d238a6f38751fad483
Story: 2005841
Task: 33613
Currently, settings in [service_available] for Monasca in tempest.conf
do not have any effect. That can lead to the situation where the
monasca-tempest-plugin is installed but monasca is not configured
which results in all monasca tempest tests failing.
With this patch, setting:
- [service_available]monasca
- [service_available]logs
- [service_available]logs-search
to "False" will skip all available tests for monasca.
If only monasca-api is available (no monasca-log-api and/or
elasticsearch), [service_available]monasca can be set to "True" and
the other 2 options ("logs" and "logs-search") to "False" so only the
monasca-api tempest tests are executed.
Depends-On: https://review.openstack.org/634308
Change-Id: I1f0cbb95765ae5fc6dca0da7af8ab56d2daf9a7f
Story: 2004917
Task: 29277
When setting [service]max_log_size in the monasca-log-api
configuration to a value larger than the default (which is 1 MB
currently), the following tempest tests fail:
- monasca_tempest_tests.tests.log_api.test_constraints.\
TestLogApiConstraints.test_should_reject_too_big_message
- monasca_tempest_tests.tests.log_api.test_constraints.\
TestLogApiConstraints.test_should_reject_too_big_message_multiline
This happens because the tempest tests assume that the maximum log
size is 1 MB but that is not always the case because
[service]max_log_size can be increased to a larger value.
So add a new configuration option in tempest.conf under the
[monitoring] section to be able to set the maximum log size. This
option (called "log_api_max_log_size") should be set to the same value
than [service]max_log_size in the monasca-log-api configuration file.
Depends-On: https://review.openstack.org/#/c/634308/
Change-Id: I893c66fd640017e6cc94298207d771a3ac3b8053
Story: 2004944
Task: 29346