-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Remove extraneous slashes from SSM paths, other typos #2765
Conversation
Did you used the default config? I used the example for multi-runner to test the setup. |
I used my own hand-written config, based on the multi-runner example. Basically I include
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kring Thanks for the fix, strang my test instance was working. But agree the script was incorrect. Tested your change on the multi-runner example as well.
available in pre release |
* Remove extraneous slash. * Remove more extraneous slashes.
* Remove extraneous slash. * Remove more extraneous slashes.
* Remove extraneous slash. * Remove more extraneous slashes.
I'm trying out v2.0.0-next.5 after using v1.18.0 successfully, and had a problem where my Windows runners failed to start up.
Connecting to the machine with SSM and looking at
c:\UserData.log
, the problem was that an extra slash was being added at the start of SSM paths. So instead of retrieving/github-actions-runner/whatever
, it would try to retrieve//github-actions-runner/whatever
and fail. So this PR removes the seemingly extraneous slashes, and now my runners are working well.It's also possible that I've misconfigured something such that
$ssm_config_path
is not supposed to start with a slash, but it does in my case. Please let me know if this might be the case.This PR also fixes a couple of typos in the powershell start-runner script.