Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1473405 - Truncated S3 objects
Truncated S3 objects
Status: CLOSED ERRATA
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW (Show other bugs)
2.3
Unspecified Unspecified
high Severity high
: rc
: 3.0
Assigned To: Orit Wasserman
vidushi
Bara Ancincova
:
Depends On:
Blocks: 1494421
  Show dependency treegraph
 
Reported: 2017-07-20 13:50 EDT by Orit Wasserman
Modified: 2017-12-05 18:38 EST (History)
8 users (show)

See Also:
Fixed In Version: RHEL: ceph-12.1.2-1.el7cp Ubuntu: ceph_12.1.2-2redhat1xenial
Doc Type: Bug Fix
Doc Text:
.Large objects are no longer truncated When creating large objects on large clusters, some of the objects were truncated at 512 KB size. Consequently, an attempt to read such objects failed with `Error 404`. This bug has been fixed, and large objects are no longer truncated. As a result, reading such objects works as expected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-05 18:38:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 20107 None None None 2017-07-20 13:50 EDT
Red Hat Product Errata RHBA-2017:3387 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-05 22:03:45 EST

  None (edit)
Description Orit Wasserman 2017-07-20 13:50:44 EDT
Description of problem:
On a large cluster, we are seeing some objects being truncated at 512kb size

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


How reproducible:


Steps to Reproduce:
1. Create a large object
2. Try to read the object


Actual results:
Error 404

Expected results:
Get the object

Additional info:
Comment 11 errata-xmlrpc 2017-12-05 18:38:03 EST
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:3387

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