You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the role is executed with a 'runner_name' already present in the organization , it fails due to a missing svc.sh file. That gives the impression something is wrong with the role. This will happen if you incidentally use the same runner name twice or try to install it on a different machine without deregistering the original. It would be helpful if the role warns that the 'runner_name' is already in use and aborts.
I would expect a warning or error that the runner_name is already in use instead of an error due to the missing svc.sh file (which is expected to be missing given that register_runner is skipped)
This removes a condition from the 'Replace registered runner' task to
allow it to replace organisation runners.
ResolvesMonolithProjects#207ResolvesMonolithProjects#145
Thank you! We ran into this today. We had to remove the existing entry in https://github.com/organizations//settings/actions/runners, and then after that the installation worked.
Summary
When the role is executed with a 'runner_name' already present in the organization , it fails due to a missing svc.sh file. That gives the impression something is wrong with the role. This will happen if you incidentally use the same runner name twice or try to install it on a different machine without deregistering the original. It would be helpful if the role warns that the 'runner_name' is already in use and aborts.
Issue Type
Bug Report
Ansible Version
Steps to Reproduce
Expected Results
I would expect a warning or error that the runner_name is already in use instead of an error due to the missing svc.sh file (which is expected to be missing given that register_runner is skipped)
Actual Results
The text was updated successfully, but these errors were encountered: