As zed is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I2f81f1801f8f7a049a6fc012c8e9455adceeb9ec
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: If2608dfec183f97727972348b72b0f72a3535b21
Since it was removed we should use assertCountEqual, but it must have a hashable elements
since it uses Counter currently we have dict which are not hashable, So we use the old version
Change-Id: Idaf0cf38ef56dfceaca6fd9f8f5ab52c27ffaf2f
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I543595c0e3145495923517101ffa057fd7bccb4c
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 compatibility but we recommend
to switch to new one.
Change-Id: I73c5f0df0854a502e06e7c45f8b4d215a0832bdf
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: Ic9c4bd70a1071fccb8b71f0c9a97e0d2bfbc12a2
swap size was reduced to all nodes this created oom when running ceilometer
increase the size to what it was before
Change-Id: I8b86ba958bab07589abf6570f2242f7fc29bdb78
for some strange reason when installing ceilometer and gnocchi
the mysqld process is killed by the oom killer of the operating system
this happens only in the gate and not localy on my devstack.
for now we won't enable the ceilometer plugin (which installs gnocchi)
Change-Id: If870b80456d8ebd4877253d977b5c59a11ad1c16
Tempest could be used not only after initial deployment but for
cloud verification during operations or after update. We don't
need to check that services are created today.
Depends-On: https://review.opendev.org/#/c/751657/
Change-Id: Ifc3cb1933a591ce1fe05fe11d5e07b78a0e61375
WHile moving the jobs to zuulv3 native, Focal migration work
got reverted- https://review.opendev.org/#/c/747109/
This commit makes stable jobs to keep running in Bionic and
master IPv6 on Focal.
Change-Id: Ibc82fbe95f6eca6f660596cf9da8c5c2e03c6fe2
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(Depends-On).
Stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html
Change-Id: Ia69f906364d6fe5a31b14dc8ec9cd37e18bdf27d
Story: #2007865
Task: #40226
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: If0c72f4b5df2ac8983401a91e468d4e3863b2ba5
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: Id1bdef61cbca373e70d34cb45287a09ecc3776bb
Dmitriy Rabotyagov