actions / actions/runner

Error messages when removing a self-hosted runner

Open
#971 23 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug papercut Runner Bug
Dominant language
C#
Stars
6.3k
Forks
1.4k
Avg merge
1d 16h
Merged PRs (30d)
24

Description

Describe the bug
When removing a self-hosted runner, I get the following error messages:

ldd: ./bin/libSystem.Security.Cryptography.Native.OpenSsl.so: No such file or directory
ldd: ./bin/libSystem.IO.Compression.Native.so: No such file or directory
# Runner removal
√ Runner removed successfully
√ Removed .credentials
√ Removed .runner
An error occurred: Access denied. System:ServiceIdentity;DDDDDDDD-DDDD-DDDD-DDDD-DDDDDDDDDDDD needs View permissions to perform the action.

The removal seems to succeed though, as refreshing the page removes the self-hosted runner from the list.

To Reproduce
Steps to reproduce the behavior:

  1. Get the removal line from "Settings" tab of the repository, then "Actions" tab, then the three-dot menu next to the self-hosted runner name, and "Remove"
  2. Run the removal line ./config.sh remove --token XXX
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Runner Version and Platform

Version of your runner?
Sorry I forgot to check, but in both cases they were downloaded from the official download links as given out in "Add runner"

OS of the machine running the runner? Linux x86_64. This has happened twice: with Ubuntu Linux 20.04 LTS and CentOS 8.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the ./config.sh remove --token XXX command on the reported Linux environments, capturing the runner version and complete output. Trace the removal path from config.sh to determine why access is denied after the runner and credentials are removed. Done means removal completes without the misleading error and the runner is absent from the repository list.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, csharp, linux
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.