A workflow with an error on or non-active conditions keeps the workflow active in DC/OS, even after deleting
tnolet opened this issue · 0 comments
tnolet commented
Situation:
- A workflow that has a typo, or has some other reason for not going to the "running" stage.
- Delete the workflow in Vamp (while the workflow status is "starting")
- Workflow is still in DC/OS
- This also works the other way around.
This is a very potential resource leak.
The screenshot show the canary workflow active in DC/OS, but non-existent in Vamp. The other workflow, event-based-trigger, is visible in Vamp but not in DC/OS.
Vamp: 0.9.5-1237-g7000ce10
DC/OS: 1.9.0
