elastic / elastic/integrations
[Subscription basic] [servicenow] Failing test daily: system test: aws in servicenow.event
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 182
Description
- Stack version: Same as in Pull Request builds
- Subscription: basic
- Package: servicenow
- Failing test: system test: aws
- DataStream: event
- 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 copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/ubuntu/manifests/sha256:33ceb71981b602c1a7443a53469e4dba065f7503eab3078a2d7a57a2ab987517: 502 Bad Gateway
```
First build failed: https://buildkite.com/elastic/integrations/builds/49345
Contributor guide
Research direction
Start with the failing system test: aws for the servicenow package and DataStream event, then review the first Buildkite failure (build 49345). Reproduce the Docker Compose setup failure and determine whether the ubuntu:24.04 image pull error is transient or requires a project change; done means the test setup and daily run pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, docker-compose
- Domain
- cloud, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100