While running tempest tests over https, warnings
are shown for unverified HTTPS request beacause
by default urllib3 don't verify ssl certificates.
So now, certification validation warnings have been
disabled.
Change-Id: I0e99af8364e262baa37a56b0a8846abde3a8d2b0
Closes-bug: #1570451
In version of oslo.messaging > 4.6.1, the __call__ method of
dispatcher.RPCDispatcher no longer exists. It is now a 'method-wrapper'
from the "object" object.
Calling inspect.getargspec on a method-wrapper doesn't work
TypeError: <method-wrapper '__call__' of ABCMeta object at 0x2cc3650> is not a Python function
Change-Id: Ie2ca1a2b9163a5edfe1e779cff462692197a471d
* Before this change there was a possibility of conflicts between
different tests working with cron triggers, especially if run
in parallel, because of using same trigger names (e.g. 'test').
To prevent such potential situations all trigger names should
be unique and generated randomly.
Change-Id: I57b0ac8072ab5f9158547fa0611a1003d1dc5e8a
Partial-Bug: #1564353
This patch fix the dir_path that helps to get the directory of
Mistral resources.
Without this patch, this is what we get when running Tempest:
IOError: [Errno 2] No such file or directory:
'/usr/lib/python2.7/site-packages/mistral_mistral/tests/resources/openstack/action_collection_wb.yaml'
With this patch:
/usr/lib/python2.7/site-packages/mistral/tests/resources/openstack/action_collection_wb.yaml
This path is correct and Tempest runs successfully.
Change-Id: Ie4bd3db8a4e729f7937a6f3c099d7c25abffcb1b
Closes-Bug: #1568413
* Added methods like await_workflow_state() and await_task_state() to
avoid using complex constructs based on _await() methods and lambdas.
* Minor style changes
Change-Id: I7f79ec819c955a5a624ff4d103bf6e97b30d9b91
* Task result proxies were needed to be able to access
task result as $.task_name. But this was deprecated in Mitaka
in favor of using task() YAQL function. So it's time to get
rid of complicated internal machinery before making further
improvements
Change-Id: I9b8c1c9ac6e9561c6aa66151011ae2f7d906179a
Implements: blueprint mistral-remove-task-result-proxies
* Transaction in on_action_complete() must not be splitted into 2 parts,
it caused the bug with after task completion logic
* Fix executor behavior so that it doesn't send an error back to engine
if a error came from engine itself. It should report back only errors
occurred with an action itself.
* YAQL and other expected Mistral exceptions in transitions should not
lead to transaction rollback and rollback of action result. For example
if action result came and it's valid but while evaluating transition
conditions we got a YAQL exception then action result should be stored
normally w/o transaction rollback and corresponding task and workflow
should fail with corresponding state_info.
* Fixed all tests
* Minor cosmetic changes
Closes-Bug: #1524477
Change-Id: I09086e40a5902bbb6c977bf195cb035e31f21246
* Method get_controller is moved out from WorkflowController class
because it's not related with its functionality directly
* Fixed tests accordingly
* "not found" test has been removed because there's no way now to
make "not found" exceptin get raised. In order to make it happen
we need to have a new workflow specification class w/o corresponding
WorkflowController implementation. So that exception is just left
just to check ourselves when we're working on a new WorkflowController
implementation.
Change-Id: I0330870e4382f01c4519b5c48e43ac50a08db338
* Before this change method acquire_lock() would override all changes
made for an entity by a concurrent transaction when calling
entity.update() although one line before it should have read this
entity from DB and update only a timestamp to acquire the lock.
The solution is just to append "FOR UPDATE" to an SQL statement
when fetching an entity from DB. In this case we don't need to
artificially update a timestamp at all.
* Unit test for MySQL or Postgres is currently impossible, all unit
tests are run against sqlite
* Adding "PYTHONHASHSEED = 0" into "venv" environment in tox.ini to
prevent sphinx from failing. It should be added to "venv" because
docs building run with command "tox -evenv -- python setup.py build_sphinx".
* Fixed minor style issues
Change-Id: Ia749f397e18e927820ff7ae6bac7d28dc2aa2ba4
With the current setup.cfg, the folder mistral_tempest_tests is not
being packaged, making it more difficult for package maintainer like
myself to run tempest tests. Please allow this change, so that I don't
have to carry such a patch in the Debian package.
Change-Id: I5c34f3516c4f171ab4f34647f1cc4a08883feacf
The pbr section in setup.cfg is not defined, so the module docs are not being
generated. This causes the 404 when clicking on the ‘Module Index’ link under
the 'Indices and Tables’ section in [0].
[0] http://docs.openstack.org/developer/mistral/
Change-Id: I337e9f6e78257a3e8e9222779dfcd600ba6cebd8
Closes-bug: #1558574