Bug 1678701 - rgw: org.apache.hadoop.fs.contract.s3a.ITestS3AContractGetFileStatus#testComplexDirActions
Summary: rgw: org.apache.hadoop.fs.contract.s3a.ITestS3AContractGetFileStatus#testComp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 4.0
Hardware: All
OS: All
low
high
Target Milestone: rc
: 4.1
Assignee: Pritha Srivastava
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-19 12:22 UTC by Matt Benjamin (redhat)
Modified: 2020-05-19 17:31 UTC (History)
10 users (show)

Fixed In Version: ceph-14.2.8-3.el8, ceph-14.2.8-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-19 17:30:41 UTC
Embargoed:
hyelloji: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:2231 0 None None None 2020-05-19 17:31:02 UTC

Description Matt Benjamin (redhat) 2019-02-19 12:22:24 UTC
Description of problem:

org.apache.hadoop.fs.contract.s3a.ITestS3AContractGetFileStatus#testComplexDirActions
[ERROR transform.XmlResponsesSaxParser (XmlResponsesSaxParser.java:doEndElement(800)) - S3 response indicates truncated results, but contains no object summaries. (...)
This error repeats and then times out.

Comment 2 Pritha Srivastava 2019-03-01 07:50:50 UTC
The test fails because by default a call is made to listObjectsv2 which is not implemented in RGW currently. So even though RGW correctly lists objects at its end, the xml output is not exactly what is expected of listObjectV2, so hadoop repeatedly makes calls to rgw to list objects and times out after a period.

So setting the list version to 1 makes the test pass. This test can be re-run once we have listObjectsV2 in our code base.

We need to set the following property in hadoop/hadoop-tools/hadoop-aws/src/test/resources/auth-keys.xml:

<property>
<name>fs.s3a.list.version</name>
<value>1</value>
</property>

Comment 3 Giridhar Ramaraju 2019-08-05 13:09:26 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 4 Giridhar Ramaraju 2019-08-05 13:10:42 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Yaniv Kaul 2020-01-13 07:07:10 UTC
Matt, if that's not a blocker, please explain why and defer to 4.1.

Comment 26 errata-xmlrpc 2020-05-19 17:30:41 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/RHSA-2020:2231


Note You need to log in before you can comment on or make changes to this bug.