Project

General

Profile

Actions

Fix #48000

closed

rgw: fix S3 API KeyCount incorrect return

Added by 玮文 胡 over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
% Done:

100%

Source:
Tags:
Backport:
octopus, nautilus
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

KeyCount should return object count + common prefix count.
see S3 example: https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html#API_ListObjectsV2_Example_5

The PR has been merged to master, but we may need to test this as stated in https://github.com/ceph/ceph/pull/37396#issuecomment-705726925


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #48003: octopus: rgw: fix S3 API KeyCount incorrect returnResolvedNathan CutlerActions
Copied to rgw - Backport #48004: nautilus: rgw: fix S3 API KeyCount incorrect returnResolvedNathan CutlerActions
Actions #1

Updated by 玮文 胡 over 3 years ago

It seems I don't have permission to set the state to "Pending Backport" as stated in https://github.com/ceph/ceph/blob/master/SubmittingPatches-backports.rst

Actions #2

Updated by Matt Benjamin over 3 years ago

  • Status changed from New to Pending Backport
Actions #3

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #48003: octopus: rgw: fix S3 API KeyCount incorrect return added
Actions #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #48004: nautilus: rgw: fix S3 API KeyCount incorrect return added
Actions #5

Updated by Nathan Cutler over 3 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

Also available in: Atom PDF