Bug 979232

Summary:	Individual recipe priority bump is cumulative for recipeset
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	scheduler	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	0.8	CC:	azelinka, junichi.nomura, qwan, tools-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:12:59 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 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).