request.schema.RequestPriority -vs- request.priority

[srimanob]

What is the difference between request.schema.RequestPriority, request.priority. In the upgrade request,
i.e. they are difference
pdmvserv_SMP-2019GEMUpg14-00001_00016_v0__150311_103715_7426.request.schema.RequestPriority = '110000'

pdmvserv_SMP-2019GEMUpg14-00001_00016_v0__150311_103715_7426.request.priority = 60000

From the request page,
https://cms-pdmv.cern.ch/mcm/requests?prepid=SMP-2019GEMUpg14-00001&page=0&shown=164282501247, the history shows that

"wm priority 2015-03-11-17-14 PdmV Service 60000", which is not clear to me and @boudoul.

In addition,

• Stat page recognize the priority of 110000, but request manager page recognize 60000.
• Action page sees 110000

[vlimant]

Hi, request.schema.RequestPriority is the value send at submission, request.priority is the current value in request manager/wmagent.
Someone (ops?) lowered the priority of the workflow by hand in request manager, and mcm syncs to it

https://cms-pdmv.cern.ch/stats/?&Col=15-20-7-11-2-8-4-5-23-9-19&PI=SMP-2019GEMUpg14-00001

see "present priority"

[srimanob]

Hi, Thanks. This is what I guess. But I don't understand

• Why they do this? It seems Dima pinged Gaelle, but they didn't discuss in ops first
• If McM syncs, why action still be block 1?
• I increased the priority in request manager page about 30 mins ago to 110,000. So it seems this one isn't synced yet.

[vlimant]

To answer what is relevant to wmcontrol : if one provides 110000 request.schema.RequestPriority=110000