-
Bug
-
Resolution: Done
-
Blocker
-
None
-
0.2.4
-
False
-
-
False
-
-
Description of the problem:
If the workflow pod gets deleted while that workflow is running then the workflow will stay stuck in active state indefinitely.
How reproducible:
100%
Steps to reproduce:
1. Deploy Orchstrator and workflows
2. Run MTA workflow
3. Go to cluster and delete the MTA workflow pod
4. Watch pod recover then go back to janus and observe workflow in Active state indefinitely.
Actual results:
If the workflow pods gets deleted while that workflow is running then the workflow will stay stuck in active state indefinitely.
Expected results:
Workflow provides good error message saying that the connection was interrupted and to try again, or the workflow picks back up where it left off and finishes.
- depends on
-
FLPATH-1167 Add persistence to workflows via software template
- Closed
- is related to
-
FLPATH-1080 Disable abort when workflow execution does not exist
- Refinement
- links to