elastic / elastic/integrations
[Stack 8.19.21-SNAPSHOT] [cisco_secure_endpoint] Failing test daily: system test: default in cisco_secure_endpoint.event
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 225
Description
- Stack version: 8.19.21-SNAPSHOT
- Package: cisco_secure_endpoint
- Failing test: system test: default
- 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 18: Get "https://docker.elastic.co/v2/observability/stream/manifests/sha256:0c1c0e80ea7e20de5e7b8877c89a4009d863120e355d3ca729079d62a09f6ca2": dial tcp 34.56.16.77:443: i/o timeout
```
First build failed: https://buildkite.com/elastic/integrations/builds/49169
Contributor guide
Research direction
Start with the cisco_secure_endpoint system test named “default” for the event DataStream and reproduce the Docker Compose setup failure. Inspect the first failed Buildkite run for the registry timeout and verify whether the service image can be pulled reliably. Done means the system test boots its service and passes without the reported Docker Compose error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100