David Moreau Simard

@strus38 FYI I've just created a troubleshooting documentation page where I include this issue: https://ara.readthedocs.io/en/latest/troubleshooting.html We can figure out how to make the exception friendlier later.

@hille721 yes, I think there is work to do to make the pages have a consistent feel in general. What bothers me is that the status is moderately misleading because...

I forgot to say why I pulled this from 1.5.8: it sort of works but as mentioned in my last comment, there needs to be some changes under the hood...

> There is no concept of a failed task: only whether it's completed or not. The checkmark could be green even if there are failed results in the task. Not...

I've rebased the patch on top of 1.5.8rc1 and included a first iteration at the API and callback implementation for working with the new "failed" task status. It works though...

I saw an opportunity to add a link to the new host and task search pages from the numbers on the playbook index so you can easily search for the...

> It works though I will review and add at least some tests, most notably for the free strategy. I was testing what this looked like with the free strategy...

I've updated the database migration to include a script that will iterate over tasks and update the status to ``failed`` if there are any failed or unreachable results for that...

I ran the migration on the live demo with 489 920 tasks and 743 983 results (across 3483 playbooks). It took almost 11 minutes to run on a fairly fast...

Oh wow, I don't know what I was thinking... it's much faster to only iterate through failed or unreachable results instead of iterating over every task: ``` $ time ./virtualenv/bin/ara-manage...