Bug 645705 - Scheduler silently discarding tasks not matching Releases tag
Summary: Scheduler silently discarding tasks not matching Releases tag
Keywords:
Status: CLOSED DUPLICATE of bug 841197
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.5
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
: 646984 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-22 09:38 UTC by Marian Csontos
Modified: 2014-08-12 04:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-03 06:36:35 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Csontos 2010-10-22 09:38:34 UTC 
Description of problem:
Tasks not matching the release are silently discarded from recipe.
Feedback is required.

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

How reproducible:
100%

Steps to Reproduce:
1. schedule a job with e.g. /CoreOS/tcsh/Sanity/upstream for RHEL5
  
Actual results:
Scheduling job succeeds.
But the tasks I wanted were missing.

Expected results:
Warning should be written to output.

Additional info:
It takes a while to realize what happened - I do not care about my jobs much until they are installed.

Problem:
How to transfer messages from Scheduler to Web-UI? XML-RPC is either pass/error.
It may require incompatible change in RPC - e.g. returning a pair (result, list-of-messages.)
Comment 1 Marian Csontos 2010-10-26 21:41:34 UTC 
*** Bug 646984 has been marked as a duplicate of this bug. ***
Comment 2 Marian Csontos 2010-10-26 21:43:03 UTC 
Zack made a good point:

> It turns out that I had a malformed Releases: field, which is obviously my
> fault. BUT, it's very, very dangerous that beaker was simply leaving that test
> out of execution without an error message: to the casual observer, my "tests"
> were passing. In reality, they were not even being run.
Comment 3 Dan Callaghan 2012-09-03 06:36:35 UTC 

*** This bug has been marked as a duplicate of bug 841197 ***
Note You need to log in before you can comment on or make changes to this bug.