Skip to content

Task status PAUSED while it should be PENDING #3290

@Mykhailenko

Description

@Mykhailenko

While fixing this issue we have noticed unexpected task status.

Steps to reproduce the problem:

  1. lock all nodes except one
  2. submit job with 2 tasks, first task should throw exception, second task depends on first, and could be simple hello world task
  3. wait until first task became "in-error"
  4. lock this single node that was not locked
  5. select "in-error" task, and click "Mark as Finished"
  6. then first task became FINISHED, and second - PAUSED.

Expected behaviour:
at the step 6, second task should be PENDING, not PAUSED (because nobody actually paused it)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions