Skip to content

[CI] FullClusterRestartIT testSingleDoc {cluster=UPGRADED} failing #111434

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

Closed
elasticsearchmachine opened this issue Jul 29, 2024 · 4 comments · Fixed by #118038
Closed

[CI] FullClusterRestartIT testSingleDoc {cluster=UPGRADED} failing #111434

elasticsearchmachine opened this issue Jul 29, 2024 · 4 comments · Fixed by #118038
Assignees
Labels
:Data Management/Data streams Data streams and their lifecycles 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

elasticsearchmachine commented Jul 29, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:full-cluster-restart:v8.15.0#bwcTest" -Dtests.class="org.elasticsearch.xpack.restart.FullClusterRestartIT" -Dtests.method="testSingleDoc {cluster=UPGRADED}" -Dtests.seed=AD9878366FDA34F -Dtests.bwc=true -Dtests.locale=fi -Dtests.timezone=America/St_Kitts -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.ResponseException: method [GET], host [http://[::1]:33969], URI [/testsingledoc/_doc/1], status line [HTTP/1.1 404 Not Found]
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [testsingledoc]","resource.type":"index_or_alias","resource.id":"testsingledoc","index_uuid":"_na_","index":"testsingledoc"}],"type":"index_not_found_exception","reason":"no such index [testsingledoc]","resource.type":"index_or_alias","resource.id":"testsingledoc","index_uuid":"_na_","index":"testsingledoc"},"status":404}

Issue Reasons:

  • [main] 3 consecutive failures in test testSingleDoc {cluster=UPGRADED}
  • [main] 2 consecutive failures in step 8.16.0_bwc-snapshots
  • [main] 2 consecutive failures in step 7.17.23_bwc-snapshots
  • [main] 9 failures in test testSingleDoc {cluster=UPGRADED} (1.8% fail rate in 513 executions)
  • [main] 2 failures in step 8.15.0_bwc-snapshots (2.6% fail rate in 77 executions)
  • [main] 2 failures in step 8.14.4_bwc-snapshots (2.6% fail rate in 77 executions)
  • [main] 2 failures in step 8.16.0_bwc-snapshots (2.6% fail rate in 78 executions)
  • [main] 3 failures in step 7.17.23_bwc-snapshots (3.8% fail rate in 80 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (7.7% fail rate in 26 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 Jul 29, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testSingleDoc {cluster=UPGRADED} (0.4% fail rate in 498 executions)

Build Scans:

@elasticsearchmachine
Copy link
Collaborator Author

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

@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 Jul 29, 2024
weizijun added a commit to weizijun/elasticsearch that referenced this issue Jul 30, 2024
* upstream/main: (105 commits)
  Removing the use of watcher stats from WatchAcTests (elastic#111435)
  Mute org.elasticsearch.xpack.restart.FullClusterRestartIT testSingleDoc {cluster=UPGRADED} elastic#111434
  Make `EnrichPolicyRunner` more properly async (elastic#111321)
  Mute org.elasticsearch.xpack.restart.FullClusterRestartIT testSingleDoc {cluster=OLD} elastic#111430
  Mute org.elasticsearch.xpack.esql.expression.function.aggregate.ValuesTests testGroupingAggregate {TestCase=<long unicode KEYWORDs>} elastic#111428
  Mute org.elasticsearch.xpack.esql.expression.function.aggregate.ValuesTests testGroupingAggregate {TestCase=<long unicode TEXTs>} elastic#111429
  Mute org.elasticsearch.xpack.repositories.metering.azure.AzureRepositoriesMeteringIT org.elasticsearch.xpack.repositories.metering.azure.AzureRepositoriesMeteringIT elastic#111307
  Update semantic_text field to support indexing numeric and boolean data types (elastic#111284)
  Mute org.elasticsearch.repositories.blobstore.testkit.AzureSnapshotRepoTestKitIT testRepositoryAnalysis elastic#111280
  Ensure vector similarity correctly limits inner_hits returned for nested kNN (elastic#111363)
  Fix LogsIndexModeFullClusterRestartIT (elastic#111362)
  Remove 4096 bool query max limit from docs (elastic#111421)
  Fix score count validation in reranker response (elastic#111212)
  Integrate data generator in LogsDB mode challenge test (elastic#111303)
  ESQL: Add COUNT and COUNT_DISTINCT aggregation tests (elastic#111409)
  [Service Account] Add AutoOps account (elastic#111316)
  [ML] Fix failing test DetectionRulesTests.testEqualsAndHashcode (elastic#111351)
  [ML] Create and inject APM Inference Metrics (elastic#111293)
  [DOCS] Additional reranking docs updates (elastic#111350)
  Mute org.elasticsearch.repositories.azure.RepositoryAzureClientYamlTestSuiteIT org.elasticsearch.repositories.azure.RepositoryAzureClientYamlTestSuiteIT elastic#111345
  ...

# Conflicts:
#	server/src/main/java/org/elasticsearch/TransportVersions.java
@fang-xing-esql fang-xing-esql added needs:triage Requires assignment of a team area label and removed :Analytics/ES|QL AKA ESQL Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Jul 31, 2024
@fang-xing-esql
Copy link
Member

This has a similar symptom/error as #111448, index_not_found_exception, send it to data management to take a look first.

@fang-xing-esql fang-xing-esql added the :Data Management/Data streams Data streams and their lifecycles label Aug 1, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Aug 1, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Aug 1, 2024
@dakrone dakrone 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 Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Data streams Data streams and their lifecycles 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.

4 participants