Bug 1319759

Summary: no explanation when no machine satisfies criteria
Product: [Retired] Beaker Reporter: Marek Haicman <mhaicman>
Component: generalAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: developCC: cbouchar, mjia
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-19 21:14:30 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:

Description Marek Haicman 2016-03-21 12:58:55 UTC 
Description of problem:
When running recipeset with HW requirements, that cannot be satisfied by any machine in the pool, beaker shows this recipeset as Aborted, but there is no explanation why this happened, and user has to guess, based on nonexistence of any logs.

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

How reproducible:
reliable

Steps to Reproduce:
1. ask for machine that does not exist
2. wait for recipeset to abort


Actual results:
Recipeset is aborted, without any explanation.

Expected results:
Recipeset is aborted, explanation that no such machine is available is provided.
Comment 2 Dan Callaghan 2016-03-22 06:04:33 UTC 
This has been requested many times in the past. The problem is that (in the current scheduler design) Beaker matches recipes with systems using a single, massive generated SQL query. When that matches no rows you get this message. But there is no good way for Beaker to determine, for any given candidate system, why it was excluded from the match and give a good human-readable description of the reasoning.
Comment 3 Marek Haicman 2016-03-22 16:27:18 UTC 
Hello Dan,
to make (my) issue clear - I understand there is no easy way to say which particular rule has biggest impact, but it would be great to have at least some simple log file stating that the recipeset is in aborted state, because it failed to find suitable machine.

In current state, user has to guess whether abort happened due to too strict requested system constrains or some beaker failure.
Comment 4 Dan Callaghan 2016-03-23 00:23:47 UTC 
Beaker does tell you this much already -- if you open the results for the aborted recipes you will see:

 Recipe ID 2584892 does not match any systems
Comment 5 Marek Haicman 2016-03-23 09:33:56 UTC 
Oh, I see it now! Would it be possible to place this message to the "System"?

I understand that it's quite cosmetic change.. but would streamline experience with beaker UI :)

[Feel free to close as notabug, in case it's not feasible, or you think it's too much effort for too little gain]