-
Notifications
You must be signed in to change notification settings - Fork 273
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
[Bug]: OpenSearch Snapshot failing checksum validation #3372
Comments
Hi, @ashwin-pc , it is possible the same issue as the PR you refered to and the comment at #2114 (comment) thanks, |
@jordarlu can we get clarification about the difference between the 2 domains? We were hesitant to change the domain for a few reasons.
Based on some of the older conversations, it appears that the reason this is happening is because we cache the checksum but not the snapshot. Cant we simply not cache the checksum and generate it for every build? seems a little weird to use a cached checksum for a build. |
Hello, @ashwin-pc .. unfortunately the cache mechanism is on CloudFront where we don't have management there as I learned, and let me add @peterzhuamazon and @gaiksaya here to keep me honest.. thanks, |
Hi @ashwin-pc can you give us the exact step to reproduce this? I want to understand the root cause of this as this has been going on before in another issue. Thanks! |
Hi @ashwin-pc Could you please help us understand what is the limitation in using ci.opensearch.org instead of artifacts.opensearch.org to download the artifact? |
Hello, there ... trying to see how we can move forward on this issue : |
Hey, sorry i have not had the time to look into that unfortunately. @kavilla has more context here, looping him in. |
thanks, @ashwin-pc ,, |
Closing this issue, @ashwin-pc @kavilla please re-open if required. Thanks |
I'm facing the same issue:
OpenSearch-Dashboard@3268e3722 |
Describe the bug
This is similar to a bug we faced earlier #2114 where the snapshot for the latest main build fails checksum validation. Related error reported on Dashboards opensearch-project/OpenSearch-Dashboards#3787. This also breaks our CI workflows.
To reproduce
Run
yarn opensearch snapshot
Expected behavior
No response
Screenshots
Host / Environment
OSD main
Additional context
No response
Relevant log output
info Installing from snapshot │ info version: 3.0.0 │ info install path: /__w/OpenSearch-Dashboards/OpenSearch-Dashboards/.opensearch/3.0.0 │ info license: oss │ info Verifying snapshot URL at https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz │ info downloading artifact from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz │ info downloading artifact checksum from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz.sha512 │ERROR artifact downloaded from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz does not match expected checksum │ expected: 16e9c818034f17dcac24017a614300952de9c1d4c99c2708e85ef7d02d646a6c452b5e4e766a115a794ea28350cca5ea746e5bf033aa23d504eddb9b06464580 │ received: f1008401e42b524768a86ecef288cd746638b205df00c2e4743f6f51475072581730aeaa96951d06c2b9c274501cc148cbe8cdae01a024479d512895f1c7b876 │ headers: │ accept-ranges: bytes │ age: 143 │ connection: close │ content-length: 240730749 │ content-type: application/x-gzip │ date: Wed, 05 Apr 2023 17:35:22 GMT │ etag: "eac155b9d05cbf94b122eaadd3cdf728-46" │ last-modified: Wed, 05 Apr 2023 01:41:18 GMT │ server: AmazonS3 │ via: 1.1 38a1b6b88186539189dcd472aa234808.cloudfront.net (CloudFront) │ x-amz-cf-id: g6rMVBFUy_TUNyC6iN5kgH_7n9gIx-CUjN6pxl1P4qB0Uv9QVOlYdg== │ x-amz-cf-pop: LAX53-P3 │ x-amz-server-side-encryption: AES256 │ x-amz-version-id: 8wlhswK4CcPrNJ39UrYyW0spN8IcwY2g │ x-cache: Hit from cloudfront │ content[500 / 240730749 base64]: H4sIAAAAAAAA/+y6c5RlzZYvmuZO27Zt27Ztm5VmpZ2Vtm3bdlbaViUreavv6X73nq+7z+h+94z7z3tz7LV2RKw5Y0SsGRO/OZaDo5m9i5mRs4klHQs9Iz0jnYq8kKKKpIIqA9A/jRgZWRk52NgIGf9Gf/3/n20mVlYmFiYWNhYWdkJGJhZ2FhYgQrZ/3hL+c3JzcTVy/rPE/9N5/rq5f8LS/m+Qw3+qf1sr43/SGfjv65+VlZHp/9f//w36x/r/T5/SW/95af9VYmRiZGRnZf2P9M/OysLBxMjO/Pf6Z2ZiYuEAIvw/1sl/hf4/rn9FGVAwVCAgKKg/baH/OQLyr0+g/1xyYqpCdFLy4gygf2HM3+ajSQQGApr+w436vzPKCclLiYupqNLLibslyjksMSKG3ST8IiB2AiayMOExwJG/QgcuNkOChnJySVwfoqwn+aYaajBbZ9apJBbnf5KR4WHuS5PMG+B2iINJ01xBjE1h5HhBQTGOkS6oWUZswZtX5iMAvI7DJQkmcYKuY8ce7FrocCA/i9Md0EAoy5E4fJo71z6NX/xKOQwV1m+Pat2XiHditfGkmNo0SXXopdNklZDW95pcquWepzce5Y8DsTMuPxv9vvG7fmWdPi6Jk+ixNHr28c2vscTBFxJm5pB9JqFJmtY=
The text was updated successfully, but these errors were encountered: