Description of problem: when running any validation in osp14, we get the stack trace of an exception: Error running validationFailed to run task [error=Failed to find workflow [name=tripleo.message.v1.send] [namespace=], wf=tripleo.validations.v1.run_validation, task=notify_running]: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mistral/engine/task_handler.py", line 63, in run_task task.run() File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 159, in wrapper result = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 390, in run self._run_new() File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 159, in wrapper result = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 419, in _run_new self._schedule_actions() File "/usr/lib/python2.7/site-packages/mistral/engine/tasks.py", line 494, in _schedule_actions timeout=self._get_timeout() File "/usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 159, in wrapper result = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/mistral/engine/actions.py", line 551, in schedule wf_spec_name=self.wf_name File "/usr/lib/python2.7/site-packages/mistral/engine/utils.py", line 91, in resolve_workflow_definition (wf_spec_name, namespace) WorkflowException: Failed to find workflow [name=tripleo.message.v1.send] [namespace=] this is already fixed upstream by the review: https://review.openstack.org/#/c/579896/ Version-Release number of selected component (if applicable): openstack-tripleo-ui-9.1.1-0.20180702224622.d3d7221.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1.run any validation
*** Bug 1611306 has been marked as a duplicate of this bug. ***
Plenty of validators are still broken, apparently due to the move to containers... Separate bugs are opened for those problems so we can close this bug. Verified: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045