Description of problem:
Due to bug 714937 fixed in 21.0, a recipe is now Aborted if any task in the recipe is Aborted. Previously it was only Aborted if all tasks in the recipe are Aborted.

As a consequence, the broken system detection logic (which is currently triggered based on the recipe status) will consider a recipe to be a "suspicious abort" if any task in the recipe is Aborted. It should only consider recipes where every task is Aborted. 

Version-Release number of selected component (if applicable):
21.0

How reproducible:
somewhat easily

Steps to Reproduce:
1. Schedule a recipe for a particular system, using a released distro, with /distribution/install and /distribution/reservesys (use a small value for the RESERVETIME parameter to make testing easier)
2. Schedule another one so that they run consecutively
3. Wait for each recipe to start and then the watchdog timer to expire

Actual results:
System is marked as broken due to two consecutive Aborted recipes.

Expected results:
System should not be marked broken because the /distribution/install task completes successfully.

Additional info:
This has a high impact because it's quite common for /distribution/reservesys to be Aborted, if the job owner does not explicitly return the system before the reservation time runs out.