Bug 979234

Summary:	Priority that is bumped by the scheduler is preserved when cloning a job.
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:	unspecified
Version:	0.8	CC:	aloughla, 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:13:41 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:45:08 UTC

Description of problem:

Priority that is bumped by the scheduler is preserved when cloning a job. This job will then be (most likely) subject to the same priority bump again. 


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


How reproducible:

Most of the time

Steps to Reproduce:
1. Submit a recipe with a single system available to it
2. clone that recipe
3. 

Actual results:

The cloned recipe will be two priorities higher than the original recipe submitted

Expected results:

Something else.

Additional info:

Comment 3 Jun'ichi NOMURA 2015-12-16 02:56:48 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).

Comment 4 Aniss Loughlam 2016-08-29 21:32:19 UTC

(In reply to Jun'ichi NOMURA from comment #3)
> 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).

can you provide the exact steps to apply this workaround? I would like to use it till beaker devs patch it

Comment 5 Jun'ichi NOMURA 2016-08-29 22:55:19 UTC

You have to be admin of beaker server to use this workaround.

1. Add this line to [global] section of /etc/beaker/server.cfg on beaker server:
   beaker.priority_bumping_enabled = False
2. Restart beakerd and httpd