Repository navigation
[CI] SLMStatDisruptionIT testCurrentlyRunningSnapshotNotRecordedAsFailure failing #155621
Description
Activity
- added:Distributed/Snapshot/RestoreAnything directly related to the `_snapshot/*` APIsAnything directly related to the `_snapshot/*` APIs>test-failureTriaged test failures from CITriaged test failures from CI
on Jul 31, 2026 elasticsearchmachine commented
on Jul 31, 2026 CollaboratorAuthorMore actionsThis has been muted on branch main
Mute Reasons:
- [main] 1 consecutive failures in test testCurrentlyRunningSnapshotNotRecordedAsFailure
- [main] 1 consecutive failures in step part2
- [main] 1 consecutive failures in pipeline elasticsearch-intake
Build Scans:
- added a commit that references this issue
on Jul 31, 2026 - addedTeam:DistributedMeta label for distributed team.Meta label for distributed team.needs:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
on Jul 31, 2026 elasticsearchmachine commented
on Jul 31, 2026 CollaboratorAuthorMore actionsPinging @elastic/es-distributed (Team:Distributed)
Root cause: TOCTOU in SnapshotLifecycleTask.WriteJobStatus. When snapshot A completes, it looks up registered snapshots that are no longer running and fetches their SnapshotInfo. If snapshot B is still in SnapshotsInProgress at lookup time it is skipped; if B then finishes before A’s cluster-state update runs, B has no SnapshotInfo and is incorrectly counted as a failure (assertStats expected 0 failed, was 1). CI also shows the warning that B was removed from the registered set by another snapshot’s cleanup.
This is a product bug (false SLM failure stats under concurrent completions), not a test-only flake. Marking as medium priority; not higher since it's for stats. Will follow up with reproduction and possible solution.
- addedmedium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releases
on Jul 31, 2026 - removedneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
on Jul 31, 2026 - added a commit that references this issue
on Aug 4, 2026 - added 2 commits that reference this issue
on Aug 5, 2026 - added a commit that references this issue
on Aug 6, 2026 - added 3 commits that reference this issue
on Aug 19, 2026 - added a commit that references this issue
on Aug 20, 2026 - added a commit that references this issue
on Aug 24, 2026 - added a commit that references this issue
on Sep 1, 2026
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-core-infra.
👀