Closed ollien closed 10 months ago
Did you manage to work around the issue?
Unfortunately not. I haven't needed this playbook since so I haven't looked much. At the time of reporting I was dealing with a single host so I just installed the runner manually.
I ran in to the same problem and it ended up being me re-using the runner name, which causes the task to skip the configuration --> no svc.sh gets generated
So basically this check working as intended: https://github.com/MonolithProjects/ansible-github_actions_runner/blob/27514626f451de58629ba9379408f70a17c7cb49/tasks/install_runner.yml#L84C24-L84C24
Hi @ollien , hard to say what happened in your case. But, since svc.sh
does not exist I would say config.sh
did not run on your destination host at all (as the svc.sh
is being created after you run config.sh
. svc.sh
is not a part of the runner's gzip file). This Ansible Role checks if the runner with the same name is already registered in your github repo/org. And only if it's not, it will run the config.sh
. To force the Role to re-run the config.sh
, use reinstall_runner: yes
.
Summary
I have a playbook that uses this role to deploy self-hosted runners to some of our development hosts. The playbook has not changed, but recent iterations seem to fail with the following (
hide_sensitive_logs
need to be turned off)It seems that Github has changed the entrypoint for the runner from
svc.sh
torun.sh
(and indeed, I do not seesvc.sh
in the runner directory). I have updated to 1.18.3 and the issue seems to persistIssue Type
Bug Report
Ansible Version
Steps to Reproduce
I have removed the org I am running this under, but I suspect this would also happen on any other org.
Expected Results
I expect the runner to start
Actual Results