runner: Error messages when removing a self-hosted runner
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:
- 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”
- Run the removal line
./config.sh remove --token XXX
- 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.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 4
- Comments: 19 (8 by maintainers)
I am experiencing same issue with actions-runner-controller on AWS EKS after trying force remove the runner. All of my runner pods are keep created and terminated itself within 2 minutes. Any updates on this or workaroud to avoid terminating the runner?
Facing the same issue via clicking the Force removal of self-runner
I am seeing runners not picking up jobs, staying idle, then exiting with this
Any update on this issue? I’m facing this issue daily with enterprise-level ephemeral self-hosted runners (containerized)… It is blocking us to implement proper runner autoscaling
Is there any plan to fix this issue? We’re facing several of these errors daily as we’re relying on ephemeral self-hosted runners…
Also of note is that it reports that the job result was Canceled, but the job was not canceled.
The ephemeral runner is removed from the org, but the
.runner
and.credentials
are still present on the runner itself, whereas before this started happening those were removed when the ephemeral runner shut down.I’ve started getting this error when an ephemeral runner on Windows finishes.
@wyphan @TingluoHuang I’m also experiencing the same error message.