Bug 984777

Summary: Update documentation to explain how does the recipe scheduling works
Product: [Retired] Beaker Reporter: Jay Vyas <jvyas>
Component: DocAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: low    
Version: 0.13CC: qwan, tools-bugs, xtian
Target Milestone: ---Keywords: Documentation, EasyFix, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 968608 Environment:
Last Closed: 2020-10-21 14:15:11 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 Jay Vyas 2013-07-16 01:41:19 UTC 
The lab controller (possibly scheduler, if so , please reassign or note below) Appears to report a misleading message when machines are in broken state. 

Specifically: Ive submitted jobs for machines which are of status "Broken", but on doing so, the controller seems to return that recipe ID's do not match any system. 

"Recipe ID 951482 does not match any systems"

To reproduce: 

1) Put a machine in the "broken" state.

2) Submit a job to commision said machine above. 

3) Observe in the web ui, that the failure message sais ""Recipe ID XXXX does not match any systems".

Forgive me if I've erroneously assigned this to the wrong component.
Comment 2 Nick Coghlan 2013-07-16 02:18:49 UTC 
Agreed, since there are additional checks involved, the error message should include a qualifier along the lines of "any system available to the scheduler for this user".

We probably won't get to this for 0.14, but we can definitely take a look for 0.15.
Comment 3 Nick Coghlan 2013-07-16 02:25:21 UTC 
As far as what "available to the scheduler for this user" actually means, that's one of the questions the forthcoming architecture guide in the Beaker 0.14 documentation should answer :)
Comment 5 Amit Saha 2014-03-20 07:55:15 UTC 
(In reply to Nick Coghlan from comment #3)
> As far as what "available to the scheduler for this user" actually means,
> that's one of the questions the forthcoming architecture guide in the Beaker
> 0.14 documentation should answer :)

Moving this to "Doc" component.