cls/rgw: fix rgw list-object-versions key-marker behavior to match s3#60068
cls/rgw: fix rgw list-object-versions key-marker behavior to match s3#60068
Conversation
|
thanks @samakshd. we have a lot of test cases for ListObjects and ListObjectVersions in https://github.com/ceph/s3-tests. can you please run those to make sure you haven't broken anything there? you can find instructions in the repo's README we'll also want to add a new test case for this specific issue, since it wasn't caught before |
Sure, will do that. Although, I see that ceph API tests is failing during CI, is that expected? |
no worries, 'ceph API tests' and 'make check' can be flaky. we'll get them green when this is ready to merge |
|
jenkins test api |
|
Hi @cbodley @adamemerson , I have executed the S3-tests on the PR branch using following way: This internally runs the test using following command: Attaching the screenshot of result Please let me know if this is the expected result or not. |
@samakshd i don't think any should fail. can you tell which test case that was? the output should say above the DeprecationWarning stuff |
Here is the corresponding log
|
|
It's giving same error on main branch also though @cbodley |
…s with key marker The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit adds the test to check the corresponding case. Issue ref: https://tracker.ceph.com/issues/68055 Fix PR: ceph/ceph#60068 Signed-off-by: Samaksh Dhingra <[email protected]>
|
Hi @cbodley, I have added the corresponding test as you asked. I have tested it by building both main and my PR branch. It is giving expected results. Please let me know if any changes are required or any other tests have to be added. Thanks. s3-tests PR: ceph/s3-tests#594 |
The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit updates RGW's behavior to make the key-marker parameter exclusive, ensuring consistent behavior between RGW and S3. Fixes: https://tracker.ceph.com/issues/68055 Signed-off-by: Samaksh Dhingra <[email protected]>
4888afc to
602a681
Compare
…match s3 While testing on previous fix, I realized that it was not correct, hence corrected it now. Signed-off-by: Samaksh Dhingra <[email protected]>
|
@cbodley I have created another PR with backup branch, in case the mess I created in this one is irreversible. Extremely sorry for creating such mess, didn't know that merge or rebase is not required after each commit, I thought since the main branch would have got stale, it would be better to rebase/merge the main and then push the commit. Link for alt PR: #60280 FYI, I have run the S3 tests on the alt PR as well, and it they passed same as above with 1 xfailed (which I researched is an expected fail I guess with some library got deprecated as I mentioned above). I have added the tests for this bug as well with key marker and version id marker in my s3-tests PR. Please let me know if anything else is required from my side. Thanks. |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
…s with key marker The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit adds the test to check the corresponding case. Issue ref: https://tracker.ceph.com/issues/68055 Fix PR: ceph/ceph#60068 Signed-off-by: Samaksh Dhingra <[email protected]>
thanks, closing this one |


The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit updates RGW's behavior to make the key-marker parameter exclusive, ensuring consistent behavior between RGW and S3.
Fixes: https://tracker.ceph.com/issues/68055
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.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 toxjenkins test windowsjenkins test rook e2e