elastic / elastic/integrations
[LogsDB] [Subscription basic] [vectra_detect] Failing test daily: system test: udp in vectra_detect.log
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
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: vectra_detect
- Failing test: system test: udp
- DataStream: log
- 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:cb5affd0ae129264ec0c6b1b8691e1dbd2c6e43961d065d570c2c22b980e3c8e": dial tcp 34.56.16.77:443: i/o timeout
```
First build failed: https://buildkite.com/elastic/integrations/builds/49175
Contributor guide
Research direction
Start with the vectra_detect system test: udp and the first Buildkite failure linked in the issue. Inspect the Docker Compose service setup and the image-manifest request that timed out, then rerun the failing test to determine whether the failure is reproducible. Done means the test completes successfully without the Docker Compose startup timeout.
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
- Mostly clear
- Newbie friendliness
- 45/100