Bug 1372800

Summary:	reason of abort hidden in task details
Product:	[Retired] Beaker	Reporter:	Ales Zelinka <azelinka>
Component:	web UI	Assignee:	Martin Styk <mastyk>
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	develop	CC:	mastyk, mjia
Target Milestone:	future_maint	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-02 09:57:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ales Zelinka 2016-09-02 18:13:03 UTC

Description of problem:
This recipe aborted without even starting the installation:

https://beaker.engineering.redhat.com/recipes/3034699#installation

The reason is that "Recipe ID 3034699 does not match any systems" but this message is not to be found in the header nor in the "Installation" tab. 

It's in the "Task" tab. And only visible once you expand one of the tasks. A task that could not have been executed since the recipe didn't run at all. Quite unintuitive.

Expected results: 

The message is visible directly on the recipe page, or, if not possible, on the "Installation" tab.

Comment 1 Roman Joost 2016-09-12 23:37:01 UTC

Some thoughts to implement this:

* We'll need code to distinguish scheduler failures and the separate failures of other components like tasks in order to put messages like these on the installation tab.
* In order to handle the old data in Beaker this will need a migration step. Test with production database, since this will probably produce high load.