Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513971 - Scheduled job with --reserve-if-fail reserved machines on which tasks are passed
Summary: Scheduled job with --reserve-if-fail reserved machines on which tasks are passed
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: general
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-16 12:08 UTC by Maryna Nalbandian
Modified: 2019-03-27 14:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
mnalband: needinfo+

Attachments (Terms of Use)

Description Maryna Nalbandian 2017-11-16 12:08:40 UTC
Description of problem:
I ran with these parametres:
<param name="wow" value="/usr/bin/bkr workflow-tomorrow --run 320120 --status PAUSED --reserve-if-fail --max=1 --old --new"/

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

How reproducible:

Steps to Reproduce:
Run wow command with above commands

Actual results:
I can see reserved recipes, that are actually passed and vice versa.
R:4473401 and R:4473387

Expected results:
Failed recipes are reserved and vice versa

Additional info:

Comment 1 Dan Callaghan 2017-11-20 04:35:33 UTC
In this one:

it seems that the /distribution/reservesys did indeed skip reserving as expected (since all tasks were passing) but for some reason the harness failed to mark that task as completed. So from Beaker's point of view that task was still running until eventually the watchdog timed out and Beaker marked it as aborted.

For some reason there is no proper console log for that recipe (maybe a problem with how the POWER8 guests are configured) so we can't tell why the call to mark the task as completed did not succeed.

In this one:,task64040513

the /distribution/reservesys task also skipped reserving but it shouldn't have, since there was a failure. Since the failure was only a few minutes before /distribution/reservesys started, this is most likely another example of bug 1369431.

Note You need to log in before you can comment on or make changes to this bug.