Bug 1431833 - Full compatibility of RGW S3 API with S3A
Summary: Full compatibility of RGW S3 API with S3A
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 2.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 2.3
Assignee: Matt Benjamin (redhat)
QA Contact: Vasu Kulkarni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-13 20:20 UTC by Uday Boppana
Modified: 2022-02-21 18:43 UTC (History)
9 users (show)

Fixed In Version: RHEL: ceph-10.2.7-11.el7cp Ubuntu: ceph_10.2.7-12redhat1xenial
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-19 13:30:38 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-3538 0 None None None 2022-02-21 18:43:33 UTC
Red Hat Product Errata RHBA-2017:1497 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.3 bug fix and enhancement update 2017-06-19 17:24:11 UTC

Description Uday Boppana 2017-03-13 20:20:50 UTC 
Description of problem:
RGW in RHCS 2.3 must work with S3A plugin  in Hadoop 2.7.3 for all HDFS activities.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Kyle Bader 2017-04-19 20:45:11 UTC 
RHCS 2.3 passes the S3A unit tests provided by Hadoop 2.7.3
Comment 6 errata-xmlrpc 2017-06-19 13:30:38 UTC 
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/RHBA-2017:1497
Comment 7 Kyle Bader 2017-07-18 04:42:47 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1471626
https://bugzilla.redhat.com/show_bug.cgi?id=1470301
Note You need to log in before you can comment on or make changes to this bug.