Skip to content
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

S3 HeadObject returns ReplicationStatus=COMPLETED while in API you have ReplicationStatus.COMPLETE #2996

Closed
lukaszlenart opened this issue Jun 29, 2023 · 2 comments
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.

Comments

@lukaszlenart
Copy link

Describe the bug

Setup a S3 bucket replication, request status of a file in the origin bucket, you will get the following response

HeadObjectResponse(AcceptRanges=bytes, LastModified=2023-06-29T12:29:53Z, ContentLength=1599, ETag="344ba12e6d2dbb1f49d5a45e8b2711ad", VersionId=rKpKRY8CABVMMa94TGixWLvj.61f_Y35, ContentType=application/octet-stream, ServerSideEncryption=AES256, Metadata={}, ReplicationStatus=COMPLETED)

the problem is when you use ReplicationStatus enum there is COMPLETE instead of COMPLETED and you are ending with UNKNOWN_TO_SDK_VERSION state.

Expected Behavior

SDK should match the status returned by the endpoint

Current Behavior

ReplicationStatus.COMPLETE != ReplicationStatus=COMPLETED

Reproduction Steps

You must have a replication between S3 buckets defined, put a file in one bucket and check its status using

HeadObjectRequest.builder().bucket(bucketNameStr).key(fileKeyStr).build()
val response = s3Client.headObject(request)

Possible Solution

No response

Additional Information/Context

No response

AWS Java SDK version used

s3-2.20.87

JDK version used

17

Operating System and version

macOS 13.4.1 (22F82)

@lukaszlenart lukaszlenart added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jun 29, 2023
@lukaszlenart
Copy link
Author

Moved to proper repo
aws/aws-sdk-java-v2#4152

@github-actions
Copy link

COMMENT VISIBILITY WARNING

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant