-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Closed
Labels
:Data Management/ILM+SLMDO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.>test-failureTriaged test failures from CITriaged test failures from CITeam:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases
Description
Build Scans:
Reproduction Line:
./gradlew ":x-pack:plugin:ilm:internalClusterTest" --tests "org.elasticsearch.xpack.ilm.DataStreamAndIndexLifecycleMixingTests.testUpdateIndexTemplateFromILMtoBothILMAndDataStreamLifecycle" -Dtests.seed=278C43E22FB0D44C -Dtests.locale=syr-Syrc-IQ -Dtests.timezone=SystemV/EST5EDT -Druntime.java=23
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
java.util.concurrent.ExecutionException: [.ds-datastream-boemntfvfhb-2025.03.14-000004] org.elasticsearch.index.IndexNotFoundException: no such index [.ds-datastream-boemntfvfhb-2025.03.14-000004]
Issue Reasons:
- [main] 2 failures in test testUpdateIndexTemplateFromILMtoBothILMAndDataStreamLifecycle (0.9% fail rate in 227 executions)
- [main] 2 failures in step part2 (7.4% fail rate in 27 executions)
- [main] 2 failures in pipeline elasticsearch-intake (7.4% fail rate in 27 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Data Management/ILM+SLMDO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead.>test-failureTriaged test failures from CITriaged test failures from CITeam:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases