Bug 1639817
Summary: | RFE: S3 v2 RESTBucketGet | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Kyle Bader <kbader> |
Component: | RGW | Assignee: | Albin Antony <aantony> |
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
Severity: | medium | Docs Contact: | Ranjini M N <rmandyam> |
Priority: | high | ||
Version: | 3.1 | CC: | aantony, cbodley, ceph-eng-bugs, ceph-qe-bugs, hyelloji, kbader, knortema, mbenjamin, nagata3333333, pasik, rmandyam, sbaldwin, sweil, tserlin, uboppana |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 4.1 | Flags: | hyelloji:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-14.2.8-3.el8, ceph-14.2.8-3.el7 | Doc Type: | Enhancement |
Doc Text: |
.AWS S3 ListObjects v2 operation provides an improved mechanism to list the objects in the S3 bucket without additional configuration
Previously, S3 protocol clients, like S3A and the awscli command-line tool, had to be configured with the older ListObjects method. With this feature, AWS S3 ListObjects v2 operation is implemented, that provides an improved mechanism to list objects in an S3 bucket.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-19 17:30:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1816167 |
Description
Kyle Bader
2018-10-16 16:32:35 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri *** Bug 1784197 has been marked as a duplicate of this bug. *** Hi Ranjini, This looks fine. Thanks Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:2231 |