-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Closed
Labels
:Distributed/Snapshot/RestoreAnything directly related to the `_snapshot/*` APIsAnything directly related to the `_snapshot/*` APIs>test-failureTriaged test failures from CITriaged test failures from CITeam:Distributed Coordination (obsolete)Meta label for Distributed Coordination team. Obsolete. Please do not use.Meta label for Distributed Coordination team. Obsolete. Please do not use.medium-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
Description
Build Scans:
Reproduction Line:
./gradlew ":x-pack:plugin:snapshot-repo-test-kit:qa:gcs:javaRestTest" --tests "org.elasticsearch.repositories.blobstore.testkit.analyze.GCSRepositoryAnalysisRestIT.testRepositoryAnalysis" -Dtests.seed=D4FDD8FEB8A26166 -Dtests.locale=blo-Latn-BJ -Dtests.timezone=Asia/Kashgar -Druntime.java=25
Applicable branches:
9.1
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
org.elasticsearch.client.ResponseException: method [POST], host [http://[::1]:36447], URI [/_snapshot/repository/_analyze?blob_count=10&seed=-5626626132371812911&max_blob_size=1mb&timeout=120s&concurrency=4], status line [HTTP/1.1 500 Internal Server Error]
{"error":{"root_cause":[{"type":"repository_verification_exception","reason":"[repository] Elasticsearch observed the storage system underneath this repository behaved incorrectly which indicates it is not suitable for use with Elasticsearch snapshots. See [https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-snapshot-repository-analyze?version=master] for further information. Elasticsearch attempted to remove the data it wrote at [temp-analysis-kvM6y_bqTEGon_P5TR45UA] but may have left some behind. If so, please now remove this data manually."}],"type":"repository_verification_exception","reason":"[repository] Elasticsearch observed the storage system underneath this repository behaved incorrectly which indicate
[truncated]
Issue Reasons:
- [9.1] 2 failures in test testRepositoryAnalysis (6.1% fail rate in 33 executions)
- [9.1] 2 failures in step third-party_gcs (66.7% fail rate in 3 executions)
- [9.1] 2 failures in pipeline elasticsearch-periodic (66.7% fail rate in 3 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/Snapshot/RestoreAnything directly related to the `_snapshot/*` APIsAnything directly related to the `_snapshot/*` APIs>test-failureTriaged test failures from CITriaged test failures from CITeam:Distributed Coordination (obsolete)Meta label for Distributed Coordination team. Obsolete. Please do not use.Meta label for Distributed Coordination team. Obsolete. Please do not use.medium-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