Skip to content

Upgrade AWS SDK to v1.12.746 #122431

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

Merged
merged 6 commits into from
Feb 17, 2025

Conversation

alex-kattathra-johnson
Copy link
Contributor

@alex-kattathra-johnson alex-kattathra-johnson commented Feb 12, 2025

No description provided.

@alex-kattathra-johnson alex-kattathra-johnson requested a review from a team as a code owner February 12, 2025 20:21
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.1.0 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Feb 12, 2025
@alex-kattathra-johnson alex-kattathra-johnson force-pushed the fixes-98201 branch 3 times, most recently from a6a0678 to 3fe7b92 Compare February 13, 2025 01:34
@alex-kattathra-johnson alex-kattathra-johnson force-pushed the fixes-98201 branch 3 times, most recently from 8daf5ab to afada68 Compare February 13, 2025 14:33
@limotova limotova added :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs and removed needs:triage Requires assignment of a team area label labels Feb 14, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Coordination Meta label for Distributed Coordination team label Feb 14, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@mhl-b
Copy link
Contributor

mhl-b commented Feb 14, 2025

We are in the process of upgrading to v2. #122062

@DaveCTurner, should we wait for v2 or it's ok to bump v1 patch version?

@DaveCTurner
Copy link
Contributor

I see no problems with upgrading this SDK version, even though it will eventually (hopefully soon) be replaced by a similarly-new-and-featureful v2.

@DaveCTurner DaveCTurner self-assigned this Feb 17, 2025
@DaveCTurner DaveCTurner added >upgrade v8.19.0 v9.0.1 auto-backport Automatically create backport pull requests when merged labels Feb 17, 2025
@DaveCTurner DaveCTurner changed the title Update aws sdk to a version that is compatible with pod identity Upgrade AWS SDK to v1.12.746 Feb 17, 2025
@DaveCTurner DaveCTurner added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Feb 17, 2025
@DaveCTurner
Copy link
Contributor

@elasticmachine ok to test

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (assuming CI is happy)

@DaveCTurner
Copy link
Contributor

@elasticmachine test this please

@DaveCTurner
Copy link
Contributor

@elasticmachine test this please

@DaveCTurner
Copy link
Contributor

@elasticmachine test this please

@elasticsearchmachine elasticsearchmachine merged commit 5462601 into elastic:main Feb 17, 2025
18 checks passed
DaveCTurner pushed a commit to DaveCTurner/elasticsearch that referenced this pull request Feb 17, 2025
DaveCTurner pushed a commit to DaveCTurner/elasticsearch that referenced this pull request Feb 17, 2025
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.x
9.0

elasticsearchmachine pushed a commit that referenced this pull request Feb 17, 2025
elasticsearchmachine pushed a commit that referenced this pull request Feb 17, 2025
ywangd added a commit to ywangd/elasticsearch that referenced this pull request Feb 18, 2025
When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With elastic#116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: elastic#122431
Relates: elastic#116212

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709
elasticsearchmachine pushed a commit that referenced this pull request Feb 18, 2025
When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With #116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: #122431 Relates: #116212 Resolves: #122799

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709
ywangd added a commit to ywangd/elasticsearch that referenced this pull request Feb 18, 2025
When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With elastic#116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: elastic#122431 Relates: elastic#116212 Resolves: elastic#122799

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709

(cherry picked from commit 850249b)

# Conflicts:
#	muted-tests.yml
ywangd added a commit to ywangd/elasticsearch that referenced this pull request Feb 18, 2025
When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With elastic#116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: elastic#122431 Relates: elastic#116212 Resolves: elastic#122799

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709

(cherry picked from commit 850249b)

# Conflicts:
#	muted-tests.yml
elasticsearchmachine pushed a commit that referenced this pull request Feb 18, 2025
* Handle status code 200 for s3 CMU response (#122815)

When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With #116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: #122431 Relates: #116212 Resolves: #122799

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709

(cherry picked from commit 850249b)

# Conflicts:
#	muted-tests.yml

* unmute
elasticsearchmachine pushed a commit that referenced this pull request Feb 19, 2025
When a CopmleteMultipartUpload request fails after the initial 200
response, the status code of the failure response use to be not set and
hence got translated to status code 0. With #116212, we handle this case
accordingly. Since AWS SDK 1.12.691, the status code is now set to 200
instead of 0. This PR changes our error handling code accordingly.

Relates: #122431 Relates: #116212 Resolves: #122799

Relevant AWS SDK change
https://github.com/aws/aws-sdk-java/blame/430899c217f34fae63b35c77f4d9bfd361c9de77/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L3696-L3709

(cherry picked from commit 850249b)

# Conflicts:
#	muted-tests.yml

Co-authored-by: Elastic Machine <[email protected]>
@alex-kattathra-johnson
Copy link
Contributor Author

@DaveCTurner Do we have an ETA on the 8.19.0 release?

@DaveCTurner
Copy link
Contributor

Sorry @alex-kattathra-johnson, no hard plans for 8.19.0 yet - we haven't even released 8.18.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs external-contributor Pull request authored by a developer outside the Elasticsearch team Team:Distributed Coordination Meta label for Distributed Coordination team >upgrade v8.19.0 v9.0.1 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants