Bug 979232 - Individual recipe priority bump is cumulative for recipeset
Summary: Individual recipe priority bump is cumulative for recipeset
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.8
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-28 02:39 UTC by Raymond Mancy
Modified: 2020-10-21 14:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 14:12:59 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 978904 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 978904

Description Raymond Mancy 2013-06-28 02:39:03 UTC
Description of problem:

When a recipeset's priority is bumped on account of a single recipe only having one system available to it, this becomes a cumulative effect when multiple recipes meet this criteria.

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


How reproducible:

Always

Steps to Reproduce:
1. Create a RS with 2 recipes, each with one system available to it
2. 
3.

Actual results:

Before the RS has been queued its priority will be two levels higher than it was originally (that's if our priority ceiling allows it).

Expected results:

Only bumped one priority.

Additional info:

Comment 3 Jun'ichi NOMURA 2015-12-16 02:56:08 UTC
Note: though the bug might still be there, it is currently non-issue for me as I'm disabling priority bump (by setting beaker.priority_bumping_enabled = False).


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