You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
May be this can be a feature request but I don't see any discussions ( of any kind) at here, so not sure where to log it. And also, It's existing functionality too.
Describe the bug
In summerwind images, If we receive a SIGTERM the runners waits default 15 mins before killing a running job. With Scaled Sets ( ARSS), helmcharts use ghcr.io/actions/actions-runner images with run.sh entrypoint which lacks the graceful termination functionality. This functionality is expected as consistent between ARC and scaled sets.
To Reproduce
Steps to reproduce the behavior:
Launch the Runner with a label.
Run a workflow with the assigned label. Make sure to have a step of bash sleep statement to simulate long running job.
Send SIGTERM signal. On kubernetes send a pod termination signal.
Check if the workflow succeeded or not.
Expected behavior
These 2 different behaviors are expected based on running is running the job or not.
Run the runner without a job assigned, SIGTERM should be propagated and runner should exit.
Run the runner with a job assigned, SIGTERM should not be propagated and runner shouldn't exit unless job is finished with a reasonable grace period.
Runner Version and Platform
2.316.1
OS of the machine running the runner? Linux - Ubuntu 22
What's not working?
SIGTERM handling
The text was updated successfully, but these errors were encountered:
May be this can be a feature request but I don't see any discussions ( of any kind) at here, so not sure where to log it. And also, It's existing functionality too.
Describe the bug
In summerwind images, If we receive a SIGTERM the runners waits default 15 mins before killing a running job. With Scaled Sets ( ARSS), helmcharts use
ghcr.io/actions/actions-runner
images withrun.sh
entrypoint which lacks the graceful termination functionality. This functionality is expected as consistent between ARC and scaled sets.To Reproduce
Steps to reproduce the behavior:
step
of bashsleep
statement to simulate long running job.Expected behavior
These 2 different behaviors are expected based on running is running the job or not.
Runner Version and Platform
2.316.1
OS of the machine running the runner? Linux - Ubuntu 22
What's not working?
SIGTERM handling
The text was updated successfully, but these errors were encountered: