On POMS integration instance the automatic submission for the second stage is queued/hold
On POMS integration instance I have the Campaign test_vito_tutorial_03; ID: 3277; VO: uboone; poms_role: analysis
I manually submit jobs for the first stage (Campaign stage: sim; ID: 2799) , then job submission from the second stage (Campaign stage: reco; ID: 2800), that depends on the first stage are, is queued and I got en email saying:
Due to an invalid proxy, we had to queue a job launch Please upload a new proxy, and release queued jobs for this campaign
But the proxy uploaded to POMS is still valid, it has been successfully used for another submission.
#1 Updated by Marc Mengel over 1 year ago
So I'm pretty sure this was the ownership problem, where submissions were showing up as belonging to to me (mengel). I think this is fixed now,but I can't test it, because I can't see the difference between it getting the ownership right (I am mengel) or wrong...
#2 Updated by Vito Di Benedetto over 1 year ago
OK, I just submitted 1 job to test the fix.
Though the job is going to fail when the final output is required to get its metadata declared to SAM.
But it looks like POMS tries to submit jobs for the next campaign stage anyway. We will see if the submission will happen or it will be aborted as there are no input files from the previous stage.
#4 Updated by Vito Di Benedetto over 1 year ago
So the test jobs went through. As expected it failed.
POMS tried to submit jobs from the second stage, this time the submission attempt succeeded, i.e. the submission was not hold as now the proxy was found.
Then the submission was aborted by POMS, as the input dataset was empty.
It looks like the issue reported here fixed.
#6 Updated by Vito Di Benedetto over 1 year ago
Yuyi Guo wrote:
So the second stage was submitted under your name/vito, not Marc?
yes, that's correct.
Though the submission was aborted by POMS as there were no files in the input dataset, this was expected.
The submission attempt is available here: