Actions
Bug #40728
closedContinuation token doesn't work in bucket list operation
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Continuation token parameter doesn't work when we use list object v2 request.
Updated by Matt Benjamin almost 5 years ago
@ali, @albin, we have s3tests that fail to check for correct behavior with continuationtoken??
Matt
Updated by Casey Bodley almost 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 28988
Updated by zhang sw almost 5 years ago
Add a test case for continuation token: https://github.com/ceph/s3-tests/pull/291
Updated by Casey Bodley almost 5 years ago
- Status changed from Fix Under Review to 7
Updated by Abhishek Lekshmanan over 4 years ago
- Status changed from 7 to Pending Backport
- Backport set to nautilus
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42280: nautilus: Continuation token doesn't work in bucket list operation added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
this fix touches code that is not present in nautilus:
commit 4ffc765c4c5debc665ade7769c4647c3a7278fd2 (ceph-ci/wip-list-objects-v2) Author: albIN7 <aantony@redhat.com> Date: Wed May 15 15:19:11 2019 +0530 rgw:listobjectsv2 ListObjectsV2 is the revised List Objects API. Returns some or all (up to 1000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. Signed-off-by: Albin Antony <aantony@redhat.com>
Updated by Nathan Cutler over 4 years ago
- Status changed from Resolved to Pending Backport
Updated by Nathan Cutler over 4 years ago
Correction: the feature is being backport to nautilus by https://github.com/ceph/ceph/pull/29849 and that PR can be said to already contain this fix.
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions