As a part of blueprint distribute-mistral-operations, we have added changes to run task with RPC. Tasks will be created in IDLE state and RPC request will be created to run tasks.
In test_task_type UT, we are using nested workflow where first task is responsible to start inner workflow, due to above changes first task is created in IDLE state so, we should wait till execution success to assert all the types of tasks getting created for this workbook.
linked-to: https://review.opendev.org/c/openstack/mistral/+/869193/
Change-Id: If8fea6184d45365c20203df945e1b092449225b8
All strings are considered as unicode literal string from Python 3.
This patch drops the explicit unicode literal (u'...')
appearances from the unicode strings.
Change-Id: I34066bcaa6d30f4a6702fd5cfff8498b68433d98
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: Ib3bea2d4db1cb1d945ee0e9e85cec1bd926de8ef
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I82d2497ef2eb25888dafa809dc0653b363aada86
Currently test_multi_vim_support_target_headers is continuously failing
possibly because of some changes in dependent libraries.
Until we sort out the problem, let's disable it so that we can unblock
the CI.
Related-Bug: #1964344
Change-Id: I1fa515ea851c38b4ace6cf3657106d22c0e9777c
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: I59551c46d943fdc5224721a8f0d8003c0ac7e8d9
* Some more adjustements to the Actions API tests related to
the Action Provider transition. Some tests have to be temporarily
disabled because there's no way to make them on both current
version of Mistral and the version including action providers.
Change-Id: I13033253d5098655a001135c8702d1b1d13e76d4
* It's part of the Action Provider refactoring. The API had to
slightly change.
* Pagination has to be still implemented.
Change-Id: Ibc26645a90101eceab507e7c7755cdd4fbbf7536
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: I3651224de022bff78840df8cd6ca95792dc5cce5
Story: #2007865
Task: #40196
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: I008d8e3aeeffb1c4ef97cca9c03599d85393aa3f
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: I4f7aa67e0663ddea6a5200a55005cf2ce5a0396e
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] e8f1876aa6/.zuul.yaml (L646)
Change-Id: I9498979712375715eab79e77a1c0e89d0efe33b5
* Backports to stable/train are now failing because tempest requires
Py3 but for some reason Py2 is provided. So we have to explicitly
define the version of Python in master because there are no
stable branches for tempest.
Change-Id: I19b57e686306b9d3f26bc5a0228ebf5d7c08bb20
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the base job 'devstack-tempest-ipv6' which will
deploy services on IPv6.
This commit adds the new job 'mistral-devstack-tempest-ipv6-only'
run on gate which is derived from 'devstack-tempest-ipv6'.
Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- 'mistral-devstack-tempest-ipv6-only' will run the tests.
- 'mistral-devstack-non-apache-tempest-ipv6-only' will run the tests.
Story: #2005477
Task: #35905
Depends-On: https://review.opendev.org/#/c/699959/
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: Iacd2d9cb5effde9a801010ce3e5f590f47f8831e
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.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: If027d55cea9fd88fadbb1539bbe713b2c2a7bd29
1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Remove unncessary "=="
Change-Id: I0008ca81b9c753d26ef97e10957a1745d340d2c0
build-openstack-sphinx-docs jobs are obsolete since some time,
use the newer build-openstack-docs-pti jobs instead - using
a template.
Update tox.ini to use proper sphinx-build invocation.
Change-Id: Idfa081711a24a6076e8b9a0ca770423d6fa62f94
Thorough replacement of git.openstack.org URLs with their opendev.org counterparts.
Change-Id: Id6768e790fbcf4e73cde4e479e0f31ed5e1a9b8d
Closes-Bug: #1826041