-
Notifications
You must be signed in to change notification settings - Fork 25
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] s3upload weirdly switch architecture value during upload sha512 for snapshots #319
[BUG] s3upload weirdly switch architecture value during upload sha512 for snapshots #319
Comments
@peterzhuamazon Is this still a valid issue? |
Hi, @peterzhuamazon .. just want to circle back with you if this issue still exists ,or if we can close it for now? As all the jennkins libs moved to |
It is still an issue and it happens transiently. |
Thank you, @peterzhuamazon , will you suggest adding some gardian code for it? or it will not help at all? maybe we validate the x64 file existinfg before uploading x64? same as arm64? thanks!! |
|
This seems more like the scope of global var due to us not assigning type. |
Will issue a potential fix to check on this. |
Re-open as there is a PR missing on the build side. |
@peterzhuamazon , could you provide the latest update on this issue. |
I'm seeing the same issue on our recent snapshot publish. https://build.ci.opensearch.org/blue/organizations/jenkins/publish-opensearch-min-snapshots/detail/publish-opensearch-min-snapshots/129/pipeline/
This is supposed to be tarball snapshot. |
Related issue: opensearch-project/opensearch-build#3097 |
In this section, I have seen weird behavior happens over time that x64 is uploading arm64, while arm64 is upload x64.
https://github.com/opensearch-project/opensearch-build/blob/main/vars/uploadMinSnapshotsToS3.groovy#L35-L37
This seems like a random error and it does not happen all the time.
But happens twice since yesterday morning already.
Acceptance Criteria
Fix the library that has causes this issue. Refactoring var scopes in uploadMinSnapshotsToS3 libs #318Thanks.
The text was updated successfully, but these errors were encountered: