Description of problem:
If I will change priority from Urgent to High in editor - when I do clone job - this change is not reflected and priority of new job is still in Urgent.
Version-Release number of selected component (if applicable):
Do and submit job with priority Urgent. Then click on clone job. Change job priority from Urgent to High. Submit changed job.
And you will see that job is running with Urgent priority - and that is wrong.
Doesn't reflect changes I did in priority of job.
If I will rewrite priority with High value job should be run with High priority.
Ping me on IRC #brno if needed.
I tried the same issue on 2 beaker portals:
Even I choose priority High or Urgent always put into job description
This happened with submitting new job from XML too.
Problem is still not fixed. If I will change priority with clone jobs new job have still the same priority as old job.
Ok, that is a slightly different problem than what you originally described.
You originally you said you were having problems going from Urgent to High.
To go above 'Normal', you need special privileges. I would assume that if you have the permission to set the job to "Urgent", then you would also be able to set it to "High".
I'm guessing though that perhaps you don't have the right permission to set the priority that high.
Is the priority getting bumped up by the scheduler due to only a single machine matching the recipe?
It could be. If it's still in the new state though than it should not have any priority bumping done on it.
Now when I'm submitting job and if it have priority High I get Normal.
When I'm cloning job - I'm putting there priority High I will get Normal.
So it is really changed.
I don't know if it is fixed because the priority are now always (by default) set to Normal.
To set priority higher than Normal, you need to be in the admin or queue_admin group. If you try and set it higher than Normal without being in these groups it will automatically go back to Normal. This is expected behaviour.