Project

General

Profile

Bug #19142

Kill submission campaign not working.

Added by Anna Mazzacane over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
02/26/2018
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Experiment:
Stakeholders:
Duration:

Description

I discussed this with Marc and understood that there are permissions issues and interactions between POMS and jobsub.

I 'm wondering if we can use (and implement) the same workflow used for submission:

user -> POMS -> exppro -> jobsub_submit

So, it will be the same for killing jobs:

user -> POMS -> exppro -> jobsub_rm

and for holding them:

user -> POMS -> exppro -> jobsub_hold

History

#1 Updated by Anna Mazzacane over 2 years ago

  • Tracker changed from Bug to Task

#2 Updated by Marc Mengel over 2 years ago

This is done in 0e2f5d42 -- we use the snapshot of the launch template used to launch the job to ssh in and setup the environment and issue jobsub_{rm,hold,release}. Technically if they're killing all jobs for a given campaign, we use the launch template used for the first launch (it might have changed partway through?) but that should still be okay.

#3 Updated by Marc Mengel over 2 years ago

  • Status changed from Assigned to Work in progress
  • % Done changed from 0 to 80

#4 Updated by Anna Mazzacane over 2 years ago

  • Tracker changed from Task to Bug

#5 Updated by Anna Mazzacane over 2 years ago

  • Status changed from Work in progress to Resolved
  • % Done changed from 80 to 100

#6 Updated by Anna Mazzacane over 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF