beats
beats copied to clipboard
elastic
Build 106 for 8.12 with status FAILURE - Error creating DB Instance: InstanceQuotaExceeded: DB Instance quota exceeded
:broken_heart: Build Failed
the below badges are clickable and redirect to their specific view in the CI or DOCS
Expand to view the summary
Build stats
-
Start Time: 2024-02-11T02:56:45.133+0000
-
Duration: 130 min 31 sec
Test stats :test_tube:
| Test | Results |
|---|---|
| Failed | 0 |
| Passed | 3245 |
| Skipped | 177 |
| Total | 3422 |
Steps errors 
Expand to view the steps failures
Terraform Apply on x-pack/metricbeat/module/aws
- Took 1 min 36 sec . View more details here
- Description:
terraform apply -auto-approve
Terraform Apply on x-pack/metricbeat/module/aws
- Took 0 min 22 sec . View more details here
- Description:
terraform apply -auto-approve
Error signal
- Took 0 min 0 sec . View more details here
- Description:
startCloudTestEnv: terraform apply failed.
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
The error Error creating DB Instance: InstanceQuotaExceeded: DB Instance quota exceeded is caused by CI hitting the RDS limit in eu-central-1 zone.
The DBs should be deleted after CI is done but some of them are not removed for some reason. I deleted the DBs that are created over a week ago so now the build should pass. But we should spend more time looking into why these orphan DBs are not deleted properly.
@bturquet could you please create a follow up issue and make sure these DBs are properly deleted after the test run?
cc @elastic/ingest-eng-prod as this is something to keep in mind for the Buildkite migration.
Sorry I forgot to create the issue! Here is the followup: https://github.com/elastic/beats/issues/38059
