[Feature] Cancel running Builds / Procedures / Actions

[mbecker20]

Sometimes you want to cancel something that takes a while to run, after its started. For Builds, this is possible when using AWS Builder, but not Server builder. Also, its not possible in any case for Action / Procedure.

Ideally cancelling a Procedure will also cancel the running underlying action. Say your Procedure including running a Build, it would be great if cancelling a Procedure would also cancel the Build.

[mdarvanaghi]

Seconding this. I have a procedure with an action that's stuck with no output. I has been running for days and it seems there's no way I can cancel it.

[maus-me]

Experiencing the same issue as mdarvanaghi with an action that was stuck and was unable to make any modification to disable the action. For anyone else that experiences this issue I wanted to share the workaround I came up with since there does not seem to be a native way of working around the issue currently.

Workaround

1. Use docker top <core_container_name>
2. Note down the "PID" of the /action-cache/<randomstring>.ts. Note: There may be more than 1 here.
3. On the docker "HOST" machine (not the container itself), run kill -9 <PID>
4. Once you have killed all the PIDs, login to Komodo webui, disable the CRON on the action and save before it runs again. Then make any needed modifications to prevent the hangup from occurring again before re-enabling.

I would love to see this as a feature or at the very least the ability to disable "Run on Startup" and/or the modification of the cron to have a soft workaround for these types of issues.

[languagegame]

Also want a way to terminate an action which is running or has stalled. Right now this appears to require either restarting the entire komodo instance or rebooting the host server.

[Proxicon]

Same, need to restart the container to get a stuck buid to "go away" its blocking a build from running.

[ZowieTao]

We reproduced the Server Builder cancellation problem on v2.2.0: manually terminating a stuck child command left Core action state locked until restart. While validating the v2.3.0 implementation, we also found a narrower remaining edge case: cancelling during the repository clone/pull stage stops Core from awaiting the request but does not terminate the Periphery-side Git process group. Filed #1579 with reproduction details and opened #1580 to propagate cancellation through the Git stage.