elastic / elastic/integrations

[LogsDB] [Stack 8.19.22-SNAPSHOT] [sentinel_one_cloud_funnel] Failing test daily: script test: routed_data_streams in sentinel_one_cloud_funnel.event

Open
#21,221 0 comments 0 reactions 0 assignees View on GitHub
automation flaky-test
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

- Stack version: 8.19.22-SNAPSHOT
- LogsDB: enabled
- Package: sentinel_one_cloud_funnel
- Failing test: script test: routed_data_streams
- DataStream: event
- Owners:
- @elastic/security-service-integrations
- @elastic/sit-crest-contractors

Failure:
```
routed_data_streams.txt:19: setting up service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 18: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied: RUN routed_data_streams
# Verify that events are correctly routed from the event data stream to
# category-specific data streams via routing rules when rerouting is enabled.
#
# The test data in minio provides:
# - 2 dns events → sentinel_one_cloud_funnel.dns (rerouted)
# - 1 process event → sentinel_one_cloud_funnel.process (rerouted)
# - 1 file event → sentinel_one_cloud_funnel.event (retained, reroute_file not enabled) (0.000s)
# Connect to the running stack. (0.189s)
# Install an agent. (24.972s)
# Start the minio service with pre-loaded test data. (1.056s)
> docker_up -profile ${CONFIG_PROFILES}/${PROFILE} -network ${NETWORK_NAME} s1cf-minio
FAIL:
```

First build failed: https://buildkite.com/elastic/integrations/builds/49550

Contributor guide

Open the contributing guide

Research direction

Start with routed_data_streams.txt and the docker_up invocation for s1cf-minio; inspect the Docker Compose profile and image reference used by this test. Run the sentinel_one_cloud_funnel routed_data_streams test after confirming the service can start, and consider the issue done when MinIO boots and the test passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose
Domain
devops, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.