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:
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).
(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
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