Self-hosted runner does not stop after getting unregistered from github
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
After deleting a runner via the api (DELETE https://api.github.com/orgs/frnde/actions/runners/ID), the runner does not stop. Instead, it tries to restart and displays a successful connection.
The runner does not appear in the registered runner list.
In previous versions the runner stopped but now the process keeps running and displays a missleading message.
Console Log Output
# Authentication
√ Connected to GitHub
# Runner Registration
√ Runner successfully added
√ Runner connection is good
# Runner settings
√ Settings Saved.
√ Connected to GitHub
Current runner version: '2.317.0'
2024-06-10 11:03:07Z: Listening for Jobs
An error occurred: Access denied. System:ServiceIdentity;DDDDDDDD-DDDD-DDDD-DDDD-DDDDDDDDDDDD needs View permissions to perform the action.
Runner listener exit with retryable error, re-launch runner in 5 seconds.
Restarting runner...
√ Connected to GitHub
2024-06-10 11:03:47Z: Runner connect error: Registration was not found or is not medium trust. ClientType: . Retrying until reconnected.
√ Connected to GitHub
√ Connected to GitHub
Runner Version and Platform
2.317.0 - Linux (X64)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with the DELETE runner API request on Linux using runner version 2.317.0, then trace the listener and restart messages shown in the console log. Done means an unregistered runner stops instead of reconnecting or displaying a misleading successful connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100