This repository was archived by the owner on Feb 8, 2024. It is now read-only.
rgw_sal_motr :[CORTX-33109] Fixed noSuchKey error in CopyObject API for IAM Policy#407
Merged
rgw_sal_motr :[CORTX-33109] Fixed noSuchKey error in CopyObject API for IAM Policy#407
Conversation
Signed-off-by: shraddhaghatol <[email protected]>
a86b54c to
22b459a
Compare
shriya-deshmukh
approved these changes
Aug 26, 2022
cdeshmukh
reviewed
Aug 26, 2022
cdeshmukh
left a comment
There was a problem hiding this comment.
Problem :
"NoSuchKey" error was returning when tried copyObject API after applying valid IAM policy on IAM user.
Add exact policy with commands, that way anyone can try recreating it.
Am fine with changes otherwise.
Author
|
retest this please |
Author
|
ran s3 ceph test suite. All tests are passed apart from known failures. Job link - |
cdeshmukh
approved these changes
Aug 26, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem :
"NoSuchKey" error was returning when tried copyObject API after applying valid IAM policy on IAM user.
Solution :
Previously in copy object API it was considering owner of destination bucket as "user id" and not the actual owner of the bucket. Fixed that by changing owner as destination bucket owner.
Sample policy example with command is given in - https://jts.seagate.com/browse/CORTX-33109?focusedCommentId=2421624&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2421624
Signed-off-by: shraddhaghatol [email protected]
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox