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
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
* 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 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
Without this change, the result can be accurate but in the wrong order,
causing a failure like:
AssertionError:
Lists differ: ['greeting', 'farewell'] != ['farewell', 'greeting']
Change-Id: Ia0f3e9fa03834feb4c87c6ac50930a0d533a19bd
With concurrent test executions it is possible that namespaced and
non-namespaced tests run at the same time, making it flaky whether
the name of the workflow is enough to identify the workflow. Using
the id should work in all cases.
Change-Id: Ib0e7d31f9a983c723704b64b1c46940aace545d7
This reverts commit 35d94fd609.
Removing the try except makes tempest not stable branch invariant and break backports.
this fixes that
Change-Id: Ib78ca25ff25addd4c19716e59f6e638dabdc7054
Stestr conf was using the wrong module name so tox would not work (I
have no idea how that passes tempest gates) So fixing that so tox works
(on an env that has tempest setup) and removed todos that the force
deletion has been merged
Change-Id: Ib47148c5e28acaae7cd5872a1af3e7d044336ea1
This is an intermediary step so the tests can work with or without
the force parameter. Once the force parameter has landed in mistral
I will remove the try except from this implementation.
Change-Id: Id935265fcbe0a3072ba2d693edf54b892173fbdf
We shouldn't need to make a distinction between CI and local run. CI
should now properly use a home directory.
Change-Id: Ie8c20203fc31b1ba9a5b3fdcd20654562d894a10
Depends-On: I10c06d3fb644c7e3026eac7a00660f0465fb0749
Also defines the devstack jobs for mistral and python-mistralclient.
Change-Id: I7eaff91b3bc3b94ca97ffc7a1ace74c86117bd07
Depends-On: I4a3068cbe765a16f6ba4b0c3e38410929ca3a14c
Needed-By: I10c06d3fb644c7e3026eac7a00660f0465fb0749
* Using class methods for setup can create issues when tests are run
concurrently. Let's use regular instance methods instead.
* Cherry-picked tempest change from mistral project:
https://review.openstack.org/#/c/527348/
Change-Id: I43a8c3bf2d565892fbd45a1efe0abbb0cf7c11d5
The current version calls the Mistral API, this seems to be unstable.
Using another std action is enough to validate that this works
correctly.
Related-Bug: #1736685
Change-Id: I2ea70b228f3240ed89c3a3d4bd991459a6736f8c
(cherry picked from commit b291e502b27eaa5ffb4d5d971fe0f6aac8f3b866)
This disables test_create_action_execution_sync.
Doing so allows us to mvoe towards a voting tempest job. We need to come
back and fix or replace this test later.
Related-Bug: #1736685
Change-Id: Icfa134d391476cad6ef925c84e93754d8a625ef2
(cherry picked from commit d53c1a983454777f8bee16806a1331bb0bd5c1cb)
This disables test_multi_vim_support_target_headers_and_service_catalog.
Doing so allows us to mvoe towards a voting tempest job. We need to come
back and fix or replace this test later.
Related-Bug: #1736685
Change-Id: Ie6a9e67837fb8c6386f915209ecf11974ab052c6
(cherry picked from commit cd37173c8c1134155e9218b67e4a68c56e79d77c)
With this filter, it will be possible to find all the workflow
executions started by a root execution.
Implements: blueprint mistral-root-execution-id
Change-Id: Ie18493c8f59f5d77107f0adf5db491b0db05cee2
(cherry picked from commit 28130bb862b33c57f5513fbe139eee3e4444fdac)
The Mistral Tempest tests have a hard-coded dependency on Mistral being present
when Tempest tests are executed.
When trying to sparse-checkout the mistral_tempest_tests folder to run
the Mistral tests as a Tempest plugin; it fails due to Mistral not
being installed as some utilities and resources which are written in
the Mistral Tempest tests are being hard referenced from Mistral
being installed in the same environment.
This patch decouples the Mistral Tempest Tests so that they can be executed in
a stand-alone mode along with the necessary resources that are required to
execute the Tempest tests.
Change-Id: Ifd6a3a65a14c4ad4736dccc3e72cd564b6f53a0a
Closes-Bug: #1714732
Google sometimes returns 302 json, causing the test to fail.
This commit switches to httpbin.
New url used in test:
https://httpbin.org/encoding/utf8
Change-Id: I095f468310c58cede509f520feb005901a48c0c6
Allow adding many workflows with the same name.
The way this works is by adding the new workflows under another
namespace.
Notice that:
1. Namespaces are not part of the mistral DSL.
2. When executing a workflow, the namespace passes down to the
subworkflow.
3. When searching for the sub-workflow definition -
If no workflow was found in the given namespace, than the defualt
namespace will be used.
4. The default namespace is an empty string.
5. The namespace property or the workflow execution will be under
params
Partially-Implements: blueprint create-and-run-workflows-within-a-namespace
Change-Id: Id248ec5906a0899d188675d002b45f6249d36d90
Tempest has made 'related_bug' decorator as stable interface.
This commit move the usage accordingly.
Change-Id: I20497d48a46195644a114dd9f6b86aca59303097
Function 'tempest.test.attr()' has moved to 'tempest.lib.decorators
.attr()' in Pike and will be removed in a future version.
This patch replaces the 'tempest.test.attr()' with the 'tempest.lib
.decorators.attr().'
Change-Id: Iba7361382ff3b3d2b055a0507af9a8a88cd4a4ce
This patch removes the redundant setUp() methods in order to
keep the code clean, In the subclass, setUp() methods has no
benefit from that, the one in superclass could satisfy that
Change-Id: I0114e4dcfe99b1c151ce84cace0fecb7952e3ef8
In tempest, alias 'admin_manager' has been moved to 'os_admin'
in version Pike, and it will be removed in version Queens [1].
[1] https://review.openstack.org/#/c/467852/
Change-Id: I9c8890b3e39648fdce01c8f3be9fdc51927dc37a
Since assertEmpty() function has already been implemented,
let's use this function instead of generic assertEqual() function.
This change makes the code and the error messages to be more readable.
Therefore it improves maintainability a little bit.
Change-Id: I953aea98b2aad21552bafcb673d7872334cc99a5