Project

General

Profile

Actions

Bug #21993

open

Workflow runner keeps running when its only subprocess is "on hold" (state=queued, priority=0)

Added by Lucas Di Pentima 12 days ago. Updated 11 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Story points:
-

Description

Steps to reproduce:

  1. Launch a workflow that starts with a single step (e.g.: revsort) and wait for the wf runner instance to start
  2. Wait for the subprocess appears as Queued
  3. Cancel the subprocess

The workflow runner instance will keep running indefinitely. Not sure if it's a-c-r's job to realize that it should cancel itself.


Files

stuck-wf.png (161 KB) stuck-wf.png Lucas Di Pentima, 07/09/2024 06:36 PM

Related issues

Related to Arvados - Bug #20985: Setting priority 0 on a queued container should change it to "cancelled" stateNewActions
Actions #1

Updated by Lucas Di Pentima 12 days ago

Actions #2

Updated by Brett Smith 12 days ago

  • Related to Bug #20985: Setting priority 0 on a queued container should change it to "cancelled" state added
Actions #3

Updated by Peter Amstutz 11 days ago

Yes, arvados-cwl-runner should notice that the priority went to 0 and do something about it.

Actions

Also available in: Atom PDF