Workflow error analysis

[Toure Dunnon]

When a workflow fails it now may be hard to quickly find a root cause.

From CLI the only way (without creating a new execution) is to use a sequence of commands like:
* 'mistral task-list <workflow execution id>' and see what are in ERROR
* for each failed task execution run 'mistral action-execution-list' and see what are in ERROR
* for each failed action run 'mistral action-execution-get-output <id>' and see the description of the error
* for each failed task execution of type Workflow, find the sub-workflow execution ID, and go back to the first bullet.

It is also possible to create and execute a workflow with a "publish" of all tasks and all sub-workflow tasks recursively (and also filter by tasks in error state). Example: http://paste.openstack.org/show/599714/

[Toure Dunnon (toure)]

Spec is up for review: https://review.openstack.org/#/c/443217/

[Dougal Matthews (d0ugal)]

Two other patches related to this:

https://review.openstack.org/455447
https://review.openstack.org/452901

[Renat Akhmerov (rakhmerov)]

This is rather a blueprint, not a bug. The right ticket is https://blueprints.launchpad.net/mistral/+spec/mistral-error-analysis