Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] ClusterStateWaitThresholdBreachTests testWaitInShrunkShardsAllocatedExceedsThreshold failing #126348

Closed
elasticsearchmachine opened this issue Apr 4, 2025 · 3 comments · Fixed by #126690
Assignees
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:ilm:internalClusterTest" --tests "org.elasticsearch.xpack.ilm.ClusterStateWaitThresholdBreachTests.testWaitInShrunkShardsAllocatedExceedsThreshold" -Dtests.seed=2BDAD0719ABA2123 -Dtests.locale=shi-MA -Dtests.timezone=Israel -Druntime.java=21 -Dtests.fips.enabled=true

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.index.IndexNotFoundException: no such index [shrink-cncc-index-rfqmtvnuxfdjt]

Issue Reasons:

  • [main] 3 failures in test testWaitInShrunkShardsAllocatedExceedsThreshold (1.0% fail rate in 296 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 119 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Data Management/ILM+SLM Index and Snapshot lifecycle management >test-failure Triaged test failures from CI labels Apr 4, 2025
elasticsearchmachine added a commit that referenced this issue Apr 4, 2025
… testWaitInShrunkShardsAllocatedExceedsThreshold #126348
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testWaitInShrunkShardsAllocatedExceedsThreshold (1.0% fail rate in 296 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 119 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@nielsbauman nielsbauman self-assigned this Apr 11, 2025
@nielsbauman nielsbauman added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 11, 2025
@nielsbauman
Copy link
Contributor

This was caused by the index existence check being run on the local node, causing the following update settings API to fail if it the master had not yet finished publishing the new cluster state. Caused by #125652. However, #126501 already fixed this so I'll put up a PR to unmute this test.

elasticsearchmachine pushed a commit that referenced this issue Apr 11, 2025
This was already fixed by #126501.

Fixes #126348
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants