https://github.com/scality/debugging-self-hosted-runner
https://github.com/scality/debugging-self-hosted-runner
Last synced: 4 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/scality/debugging-self-hosted-runner
- Owner: scality
- Created: 2021-06-24T15:09:57.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2021-07-01T01:07:29.000Z (almost 5 years ago)
- Last Synced: 2025-02-23T22:21:04.648Z (over 1 year ago)
- Language: Dockerfile
- Size: 3.91 KB
- Stars: 0
- Watchers: 35
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# debugging-self-hosted-runner
## The script
This repository aims to show an issue we are facing by using self-hosted runners.
It installs and run a self-hosted runner in a docker container with `./run.sh --once`
When the runner finish the job and stop, we try to delete it with `./config.sh remove`.
Then it configures a new runner for the next action.
## The error
A problem occurred, some time, when we try to remove a runner. It returns us an error, saying the job is busy, the same error occurred with the force delete API call. An action is linked to the runner even if he is offline and this fail the whole workflow.
Error from the runner:
```
Failed: Removing runner from the server
Runner "********" is still running a job"
```
Error on github.com:
```
The self-hosted runner: ******** lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
```
Error with the API:
```
{
"message": "Bad request - Runner "********" is still running a job\"",
"documentation_url": "https://docs.github.com/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization"
}
```
## What we are expecting
One of this call should delete the runner, no action should be linked to this runner after the job has ran. And should delete it even if an action is linked to it.
# Test it
Start the script with
```shell
./run.sh
```
then run the action which is in the `.github/workflows` folder.