-
-
Notifications
You must be signed in to change notification settings - Fork 338
config.toml has empty "gitlab-runner-parent-id" #496
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
Comments
We switched to IMDv2 with a require token. Did you checked if the token passed? See https://github.com/npalm/terraform-aws-gitlab-runner/blob/9d39138b7f526ebe7132c5d0bb1e4a50cea50626/template/logging.tpl#L40 |
Yes, indeed, the logs show that all the other calls for the instance ID work, but the one in gitlab-runner.tpl doesn't. Mabye you just didn't adjust that file during the switch as it is still showing this in the master branch: Maybe it's enough to remove this line (Line 2 of the file) and adjust Line 3 to use the instanceId variable that's alreayd there? Edit:
to
or
|
Hi,
I've found that, for what ever reason, the user-data configuration doesn't seem to get the instance ID of the gitlab runner agent.
This variable
https://github.com/npalm/terraform-aws-gitlab-runner/blob/9d39138b7f526ebe7132c5d0bb1e4a50cea50626/template/gitlab-runner.tpl#L3
contains
gitlab-runner-parent-id,
.This is also what the log says:
The curl call in the log to the instance-id endpoint show this:
All other calls to metadata or getting the accesstokens work. It's just this one.
Funnily enough, a few lines above in the log, there is a call to
http://169.254.169.254/latest/dynamic/instance-identity/document
which return the instance-id. So maybe the metadata isn't available at this point in the EC2 creation process?I can reproduce this issue with every deployment.
The text was updated successfully, but these errors were encountered: