Bug 1369599

Summary: priority bumping is not recorded in job activity
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: schedulerAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: dcallagh, dowang, mjia, rjoost
Target Milestone: 23.3Keywords: EasyFix, Patch, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 06:44:36 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 Dan Callaghan 2016-08-23 22:44:56 UTC 
When a recipe matches only a single system, the scheduler bumps its priority as a kind of heuristic to give more weight to recipes which need rare hardware. However when that happens it's not recorded in the job activity, so it's hard to see why your recipe set priority is magically changed to some different value than what you originally submitted.

If the scheduler changes the priority on a recipe set it should be recorded in job activity as a change made by user=None service=Scheduler showing the changed priority.

See also bug 979234.
Comment 2 Dan Callaghan 2016-10-04 07:20:07 UTC 
http://gerrit.beaker-project.org/5294
Comment 5 Dan Callaghan 2016-11-07 06:44:36 UTC 
Beaker 23.3 has been released.