- 30 Sep, 2021 1 commit
-
-
Thomas Goirand authored
-
- 30 Aug, 2021 2 commits
-
-
Thomas Goirand authored
-
Thomas Goirand authored
vitrage-tempest-plugin 5.4.0 release meta:version: 5.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: Ghanshyam Mann <gmann@ghanshyammann.com> meta:release:Change-Id: I546921d83610f268a41104e0572e36ca7ed2435d meta:release:Code-Review+1: Eyal <eyalb1@gmail.com> meta:release:Code-Review+2: 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>
-
- 16 Aug, 2021 1 commit
-
-
Thomas Goirand authored
-
- 28 May, 2021 1 commit
-
-
XinxinShen authored
UPPER_CONSTRAINTS_FILE is old name and deprecated [1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file Change-Id: Ib0faeee98c348eb83354994aee9cff62e839eb3e
-
- 27 Apr, 2021 1 commit
-
-
maaoyu authored
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
-
- 20 Apr, 2021 1 commit
-
-
zhangboye authored
Moving on py3 as the default runtime for tox to avoid to update this at each new cycle. Change-Id: I38a488598b9ecbeb2dfae42cb7279c7f4710bb31
-
- 30 Mar, 2021 2 commits
-
-
Thomas Goirand authored
-
Thomas Goirand authored
vitrage-tempest-plugin 5.3.0 release meta:version: 5.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: Idef26eb60c460eb3518b3238263fbfcb96a8d1c8 meta:release:Code-Review+1: Eyal <eyalb1@gmail.com> meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com> meta:release:Code-Review+1: Ghanshyam Mann <gmann@ghanshyammann.com> meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org> meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>
-
- 20 Mar, 2021 1 commit
-
-
Eyal authored
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
-
- 16 Mar, 2021 1 commit
-
-
Eyal authored
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
-
- 15 Mar, 2021 1 commit
-
-
Eyal authored
for some reason mistral api stoppped working in gate need to investigate Change-Id: Ic0793b518cb8545d8aed6af15dc721f141cfce49
-
- 09 Mar, 2021 2 commits
-
-
Thomas Goirand authored
-
Thomas Goirand authored
vitrage-tempest-plugin 5.2.0 release meta:version: 5.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: I115150cf097287605e5fe124ca8dc70549f59726 meta:release:Code-Review+1: Eyal <eyalb1@gmail.com> meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com> meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org> meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>
-
- 19 Jan, 2021 1 commit
-
-
Eyal authored
heat fixed the image name Change-Id: Idb16a1d7dd5c093f074fb6668f67205bb4068e99
-
- 14 Jan, 2021 1 commit
-
-
wangzihao authored
This reverts commit 021dab33. Reason for revert:Python 3.7 *is* supported because it falls in the range of supported Python versions (3.6-3.8) [1]. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019648.html Change-Id: I4ebd30942c35dc10222c17525fbd80285fe29278
-
- 12 Jan, 2021 1 commit
-
-
Eyal authored
Change-Id: I61e1f44aa786b99a46e480cbbfd518a503a3baa0
-
- 08 Jan, 2021 3 commits
-
-
Zuul authored
-
Eyal authored
Change-Id: I68dab875e88b6dbdeb9ff453e60035137df7dfbd
-
Hervé Beraud authored
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. Also removing useless requirements, and pulling them from the right place. [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 Depends-On: https://review.opendev.org/c/openstack/vitrage-tempest-plugin/+/769917 Change-Id: Ia841a2d4198b43bac46a5b5af01f52e1354eea4a
-
- 05 Jan, 2021 2 commits
-
-
Zuul authored
-
XinxinShen authored
Remove python3.7 from setup.cfg, since Wallaby's python supported runtimes are python 3.6 and python 3.8[1]: [1]: https://governance.openstack.org/tc/reference/runtimes/wallaby.html Change-Id: I90f65e3b76332803f2f9b0367b1c77d5c677159f
-
- 04 Jan, 2021 1 commit
-
-
Eyal authored
Change-Id: I3320623bce9a3351cac91d5b4c1d30fbb999e5b1
-
- 03 Jan, 2021 1 commit
-
-
Q.hongtao authored
Change-Id: I5995ba0dc020fa40ddf66b7ac9f36220967b670e
-
- 22 Dec, 2020 1 commit
-
-
Eyal authored
Change-Id: Idcd726767060197f44311b605a9b28a0d6e736f0
-
- 18 Oct, 2020 3 commits
-
-
Thomas Goirand authored
-
Thomas Goirand authored
-
Thomas Goirand authored
-
- 05 Oct, 2020 4 commits
-
-
Thomas Goirand authored
-
Thomas Goirand authored
-
Thomas Goirand authored
-
Thomas Goirand authored
vitrage-tempest-plugin 5.1.0 release meta:version: 5.1.0 meta:diff-start: - meta:series: victoria meta:release-type: release meta:pypi: no meta:first: no meta:release:Author: Sean McGinnis <sean.mcginnis@gmail.com> meta:release:Commit: Sean McGinnis <sean.mcginnis@gmail.com> meta:release:Change-Id: I0fc6e0c4fea186a31c24bc879cec193fe13752dd meta:release:Code-Review+1: Eyal <eyal.bar-ilan@nokia.com> 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>
-
- 22 Sep, 2020 1 commit
-
-
Zuul authored
-
- 21 Sep, 2020 4 commits
-
-
Zuul authored
-
Eyal authored
swap size was reduced to all nodes this created oom when running ceilometer increase the size to what it was before Change-Id: I8b86ba958bab07589abf6570f2242f7fc29bdb78
-
Q.hongtao authored
Replace the following items with Python 3 style code. - six.moves.BaseHttpServer - six.moves.zip - six.PY2 - six.viewitems Change-Id: If68cc2778bfccc56248ab8fba3de764044a707e9
-
Q.hongtao authored
Change-Id: I82bd58c804c7f8b2dd2f77954489cfa3f2c42060
-
- 17 Sep, 2020 2 commits
-
-
Zuul authored
-
Eyal authored
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
-
- 16 Sep, 2020 1 commit
-
-
Ivan Kolodyazhny authored
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
-