Skip to content

[CI] SystemIndicesUpgradeIT testUpgradeSystemIndexAndDataStream failing #125168

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

Open
elasticsearchmachine opened this issue Mar 18, 2025 · 2 comments · Fixed by #125241
Open

[CI] SystemIndicesUpgradeIT testUpgradeSystemIndexAndDataStream failing #125168

elasticsearchmachine opened this issue Mar 18, 2025 · 2 comments · Fixed by #125241
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 18, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:rolling-upgrade:v8.0.1#oldClusterTest" -Dtests.class="org.elasticsearch.upgrades.SystemIndicesUpgradeIT" -Dtests.method="testUpgradeSystemIndexAndDataStream" -Dtests.seed=6AC391FFC14AB04A -Dtests.bwc=true -Dtests.locale=en-GG -Dtests.timezone=Etc/GMT+10 -Druntime.java=24

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.ResponseException: method [GET], host [http://127.0.0.1:41521], URI [.fleet-actions-results/_count], status line [HTTP/1.1 503 Service Unavailable]
{"error":{"root_cause":[{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"50bgkFHgTY-CuQFDxOMAIw","shard":"0","index":".ds-.fleet-actions-results-2025.05.06-000001"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":".ds-.fleet-actions-results-2025.05.06-000001","node":null,"reason":{"type":"no_shard_available_action_exception","reason":null,"index_uuid":"50bgkFHgTY-CuQFDxOMAIw","shard":"0","index":".ds-.fleet-actions-results-2025.05.06-000001"}}]},"status":503}

Issue Reasons:

  • [8.19] 5 consecutive failures in step 8.0.1_bwc
  • [8.19] 5 failures in test testUpgradeSystemIndexAndDataStream (0.5% fail rate in 962 executions)
  • [8.19] 5 failures in step 8.0.1_bwc (100.0% fail rate in 5 executions)
  • [8.19] 5 failures in pipeline elasticsearch-periodic (100.0% fail rate in 5 executions)

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

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 18, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@mark-vieira mark-vieira linked a pull request Mar 19, 2025 that will close this issue
@ldematte ldematte added the low-risk An open issue or test failure that is a low risk to future releases label Mar 28, 2025
@ldematte
Copy link
Contributor

Same as #125623

@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants