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] CrossClusterEsqlRCS1UnavailableRemotesIT testEsqlRcs1UnavailableRemoteScenarios failing #118350

Open
elasticsearchmachine opened this issue Dec 10, 2024 · 3 comments · May be fixed by #120388
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

gradlew ":x-pack:plugin:security:qa:multi-cluster:javaRestTest" --tests "org.elasticsearch.xpack.remotecluster.CrossClusterEsqlRCS1UnavailableRemotesIT.testEsqlRcs1UnavailableRemoteScenarios" -Dtests.seed=A423397337C6646C -Dtests.locale=en-GD -Dtests.timezone=Atlantic/Cape_Verde -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a string containing "connect_transport_exception"
     but: was "method [POST], host [http://[::1]:50649], URI [_query], status line [HTTP/1.1 500 Internal Server Error]
{"error":{"root_cause":[{"type":"node_disconnected_exception","reason":"[][[::1]:50919][indices:data/read/esql/resolve_fields] disconnected"}],"type":"node_disconnected_exception","reason":"[][[::1]:50919][indices:data/read/esql/resolve_fields] disconnected"},"status":500}"

Issue Reasons:

  • [main] 3 failures in test testEsqlRcs1UnavailableRemoteScenarios (0.4% fail rate in 851 executions)
  • [main] 2 failures in step part-4 (0.6% fail rate in 341 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.6% fail rate in 340 executions)

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

@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI labels Dec 10, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testEsqlRcs1UnavailableRemoteScenarios (0.4% fail rate in 851 executions)
  • [main] 2 failures in step part-4 (0.6% fail rate in 341 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.6% fail rate in 340 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Dec 10, 2024
…lableRemotesIT testEsqlRcs1UnavailableRemoteScenarios #118350
@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 10, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-analytical-engine (Team:Analytics)

@craigtaverner craigtaverner added Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch :Search Foundations/CCS and removed Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) :Analytics/ES|QL AKA ESQL labels Jan 17, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-foundations (Team:Search Foundations)

@quux00 quux00 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 Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants