<@U01ADKHBJKC> broke the AWS's us-west-2a's C5 ins...
# contributing-to-airbyted
Davin Chia (Airbyte)
06/18/2021, 2:20 AM
@Jared Rhizor (Airbyte) broke the AWS's us-west-2a's C5 instance types
Copy code
Error: AWS EC2 instance starting error
33
Error: InsufficientInstanceCapacity: We currently do not have sufficient c5.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get c5.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.
34
Error: We currently do not have sufficient c5.2xlarge capacity in the Availability Zone you requested (us-east-2a). Our system will be working on provisioning additional capacity. You can currently get c5.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2b, us-east-2c.u
user
06/18/2021, 2:20 AMin case any one is worried, we only spun up 20-ish instances before this happened
u
user
06/18/2021, 2:23 AMthis is common 😅 they are spot instances and not on-premise right? there is a dashboard where you can check spot instances availability
u
user
06/18/2021, 2:25 AMIt’s just funny to hit these limits with such low numbers. Only hit these types of errors on GCP with hundreds of machines that were much beefier than these.
e
Eugene Kulak
06/18/2021, 6:44 PM
we only spun up 20-ish instances before this happenedI am still running into this issue. Do we spin up more now?
u
user
06/18/2021, 6:45 PMWe could change the instance type to something that might be more available
u
user
06/18/2021, 6:45 PMWe aren’t hitting our own limits (if it’s the same error)
u
user
06/18/2021, 6:48 PMOh, maybe the issue I am seeing is not related to this then.
Is this related? https://github.com/airbytehq/airbyte/pull/4163/checks?check_run_id=2860941551
u
user
06/18/2021, 6:49 PMError: GitHub self-hosted runner registration error
Checking...
Error: A timeout of 5 minutes is exceeded. Your AWS EC2 instance was not able to register itself in GitHub as a new self-hosted runner.
u
user
06/18/2021, 6:49 PMHmm
e
Eugene Kulak
06/18/2021, 6:49 PM
I don’t think that’s limit related? You have an instance, it just can’t interact with GitHub for some reason?
u
user
06/19/2021, 12:40 AMthat's not aws related. are you still hitting it?
u
user
06/19/2021, 12:43 AMI think all builds are failing
u
user
06/19/2021, 12:43 AMI haven’t touched it
u
user
06/19/2021, 12:45 AMI've seen this before
u
user
06/19/2021, 12:45 AMthis is a bug in the action libs
u
user
06/19/2021, 12:45 AMe
Eugene Kulak
06/19/2021, 12:50 AM
we should patch it in the original lib ^
u
user
06/19/2021, 12:50 AMI'm fixing this
5 Views