elastic / elastic/integrations

[Subscription basic] [sentinel_one_cloud_funnel] Failing test daily: script test: routed_data_streams in sentinel_one_cloud_funnel.event

Closed
#21,230 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: Same as in Pull Request builds
- Subscription: basic
- 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.203s)
# Install an agent. (23.606s)
# Start the minio service with pre-loaded test data. (1.719s)
> docker_up -profile ${CONFIG_PROFILES}/${PROFILE} -network ${NETWORK_NAME} s1cf-minio
FAIL:
```

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

Contributor guide

Open the contributing guide

Research direction

Run script test: routed_data_streams and start with routed_data_streams.txt:19, where docker_up launches s1cf-minio through Docker Compose. Check why the minio/minio image cannot be pulled in the test environment; done means the service boots and the routed_data_streams test completes successfully.

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
Needs clarification
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.