Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

No instance are being created.#2738

Unanswered
AayushbajajCAW asked this question inQ&A
Dec 9, 2022· 2 comments· 3 replies
Discussion options

I have been trying to test and implement self hosted runners but the issue is that instances are turning on even after everything is connected. I have followed every step github apps and everything but still the instances are not turning up. Cloudwatch registers the request but for some reason the request to create instances are not working. I have attached the main.tf file clould anyone please help in sorting this issue out.
The main.tf file

terraform {  required_providers {    aws = {      source  = "hashicorp/aws"      version = "4.44.0"    }  }}provider "aws" {  region     = var.aws_region  access_key = "access_key"  secret_key = "secret_key"}data "aws_caller_identity" "current" {}resource "random_id" "random" {  byte_length = 20}resource "aws_iam_service_linked_role" "spot" {  aws_service_name = "spot.amazonaws.com"}module "github-runner" {  create_service_linked_role_spot = true  source  = "philips-labs/github-runner/aws"  version = "2.0.0-next.1"  aws_region = var.aws_region  vpc_id     = module.vpc.vpc_id  subnet_ids = module.vpc.private_subnets  prefix = var.prefix  github_app = {    key_base64     = "key"    id = "id"    webhook_secret = random_id.random.hex  }  webhook_lambda_zip                = "lambdas-download/webhook.zip"  runner_binaries_syncer_lambda_zip = "lambdas-download/runner-binaries-syncer.zip"  runners_lambda_zip                = "lambdas-download/runners.zip"  enable_organization_runners = true  runner_extra_labels         = "default,example"  # enable access to the runners via SSM  enable_ssm_on_runners = true  instance_types = ["m5.large", "c5.large"]  # Uncomment to enable ephemeral runners  runner_run_as = "ubuntu"  enable_ephemeral_runners = false  # enabled_userdata         = true  delay_webhook_event      = 0  runners_maximum_count = 20  idle_config = [{    cron      = "* * o-23 * * *"    timeZone  = "Europe/Amsterdam"    idleCount = 3  }]  # fifo_build_queue = true  enable_job_queued_check = true  # override scaling down  scale_down_schedule_expression = "cron(* * * * ? *)"}

Could anyone point to what i am doing worng it would be great help thanks in advnace

You must be logged in to vote

Replies: 2 comments 3 replies

Comment options

I am having similar issue, webhook and scaleup lamdas are triggered, but no instances created

You must be logged in to vote
3 replies
@Fgerthoffert
Comment options

Did you look at the logs in Cloudwatch ? there is quite a bit of detail there.

@zimml
Comment options

Same issue for me

@dtlary25
Comment options

same issue here. runners are not created. cloudwatch logs for dev-syncer says

{"errorType":"Error","errorMessage":"Cannot find GitHub release asset.","stack": ["Error: Cannot find GitHub release asset.","    at /var/task/index.js:654:15","    at Generator.next (<anonymous>)","    at fulfilled (/var/task/index.js:550:58)","    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"    ]}

and dev-scale-down

{"errorType":"TypeError","errorMessage":"Cannot set properties of undefined (setting 'scaleUp')","stack": ["TypeError: Cannot set properties of undefined (setting 'scaleUp')","    at 30873 (/var/task/index.js:61201:24)","    at __nccwpck_require__ (/var/task/index.js:66346:43)","    at /var/task/index.js:66431:37","    at Object.<anonymous> (/var/task/index.js:66434:12)","    at Module._compile (node:internal/modules/cjs/loader:1256:14)","    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)","    at Module.load (node:internal/modules/cjs/loader:1119:32)","    at Module._load (node:internal/modules/cjs/loader:960:12)","    at Module.require (node:internal/modules/cjs/loader:1143:19)","    at require (node:internal/modules/cjs/helpers:119:18)"    ]}
Comment options

I had this same issue but it turned out in cloudwatch logs no capacity was available in the region

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
6 participants
@AayushbajajCAW@lionslair@Fgerthoffert@zimml@dtlary25@swiftain

[8]ページ先頭

©2009-2025 Movatter.jp