opensearch-project/OpenSearch
Voir sur GitHub[BUG] Improper status codes for snapshot executions
Open
#4 687 ouverte le 5 oct. 2022
CCIbugdistributed frameworkgood first issuehacktoberfest
Métriques du dépôt
- Stars
- (8 123 stars)
- Métriques de merge PR
- (Merge moyen 5j 9h) (266 PRs mergées en 30 j)
Description
Describe the bug A missing S3 bucket for the snapshot results on a 500 its possible that the bucket has been deleted after association.
{
"error": {
"root_cause": [
{
"type": "repository_exception",
"reason": "[snapshot-name] could not read repository data from index blob"
}
],
"type": "repository_exception",
"reason": "[snapshot-name] could not read repository data from index blob",
"caused_by": {
"type": "i_o_exception",
"reason": "Exception when listing blobs by prefix [index-name]",
"caused_by": {
"type": "amazon_s3_exception",
"reason": "amazon_s3_exception: The specified bucket does not exist (Service: Amazon S3; Status Code: 404; Error Code: NoSuchBucket; Request ID: V3DXMMJXXXXXX; S3 Extended Request ID: D7W3ThAkomdyqtKj0msy1g1Q/qpU0h9XXXXXXXX)"
}
}
},
"status": 500
}
Then a concurrent snapshot exception is a 503
Expected behavior Errors which are client side misconfiguration or client side operations which aren't supported based on the system's concurrency specification should be a 4xx