Bug #10080
closed
pipeline_instance state can be changed from `Complete` to `Paused`
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
Updated by Radhika Chippada over 7 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.
Updated by Tom Morris over 6 years ago
- Target version set to Arvados Future Sprints
Updated by Peter Amstutz over 4 years ago
- Target version deleted (
Arvados Future Sprints) - Status changed from New to Closed