Conversation
|
ok you mean to bypass/force-complete/on-hold through the command line tool directly instead of adding it in the json files? |
|
with this PR, the afs files are totally deprecated and one adds something with ./wtcActions.py --action hold --keyword <workflow name, or keyword> using --pop option to remove it from the DB. |
|
if you are happy with the way to set these up via the command line, we merge and move on. |
|
definitely solving #273 as then one just needs to pop the action in the command line |
|
I think we can do this. It is better in all ways. Also I guess for #273 you mean we just pop it out right? |
|
@vlimant what is the keyword here? I mean it should be name of the original workflow only right? |
|
either the workflow name of some text that is found in workflow names. |
|
ok great.. thanks ... I'll try this out once I have some request we need to bypass/force-complete/keep on hold. I will also add this to the twiki so it would be helpful |
|
@thongonary FYI |
|
if there are no entries to bypass/hold/force from your end atm, we should just purge the records |
|
@vlimant I was trying to put a workflow on hold and it is giving me permission denied! Can you please have a look? |
|
So just to update for future reference - we need the proxy and export PYTHONPATH=$PYTHONPATH:/usr/lib64/python2.7/site-packages as it is a unified script. |
|
@vlimant can you please confirm that since we are using the wtcActions.py and soon the JIRA search(once tested and merged), we don't need https://github.com/CMSCompOps/WmAgentScripts/blob/master/utils.py#L6563 and https://github.com/CMSCompOps/WmAgentScripts/blob/master/utils.py#L6497 and can be commented(probably removed) from the code? |
|
the file interface is completely unused already anyways, so those can go away |
|
Thanks @vlimant @sharad1126 |
goes in the direction of #360 . @sharad1126 you should get used to the command line tool.
there are some cleanup to be finalized so that we delete elements from the db when the workflow(s) go out of scope