Bug #10080

pipeline_instance state can be changed from `Complete` to `Paused`

Added by Joshua Randall over 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
09/15/2016
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

I think transitioning the state of a pipeline_instance from `Complete` to `Paused` should be an invalid transition (i.e. trying to update a pipeline_instance with '{"state":"Paused"}' when '{"state":"Complete"}' should result in an error.

At the moment, using the CLI, I can update a pipeline instance between `Complete` and `Paused` state (and back again).

Perhaps only the following state transitions should be legal?

RunningOnServer->Complete
RunningOnServer->Failed
RunningOnServer -> Paused
Paused -> RunningOnServer

History

#1 Updated by Radhika Chippada over 2 years ago

We actually have a test in services/api/test/unit/pipeline_instance_test.rb ("update attributes for pipeline") which unfortunately updates the state of a pipeline instance from "Complete" to "Failed" and verifies that it passes. I just played with it, and I was also able to update the state to Paused as well.

#2 Updated by Tom Morris over 1 year ago

  • Target version set to Arvados Future Sprints

Also available in: Atom PDF