elastic / elastic/integrations
[LogsDB] [Subscription basic] [carbon_black_cloud] Failing test daily: system test: aws in carbon_black_cloud.alert_v7
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 225
Description
- Stack version: maximum of either the version used in PR builds or 8.17.0 (GA version for LogsDB index mode)
- LogsDB: enabled
- Subscription: basic
- Package: carbon_black_cloud
- Failing test: system test: aws
- DataStream: alert_v7
- Owners:
- @elastic/security-service-integrations
- @elastic/sit-crest-contractors
Error:
```
could not setup service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 17: failed to solve: ubuntu:24.04: failed to resolve source metadata for docker.io/library/ubuntu:24.04: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Alibrary%2Fubuntu%3Apull&service=registry.docker.io: 502 Bad Gateway
```
Latest issue closed for the same test: https://github.com/elastic/integrations/issues/18893
First build failed: https://buildkite.com/elastic/integrations/builds/49346
Contributor guide
Research direction
Start by rerunning the carbon_black_cloud system test: aws for the alert_v7 DataStream and inspect the Docker Compose setup failure while resolving the ubuntu:24.04 image metadata. Done means the test can boot its service and completes successfully without the Docker registry authorization error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, ubuntu
- Domain
- devops, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100