Bug 1660962

Summary: rgw does not support delimiter as a string it only supports a single character [consulting]
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: medium    
Version: 3.1CC: agunn, anharris, cbodley, ceph-eng-bugs, ceph-qe-bugs, jgalvez, kbader, mbenjamin, pasik, sweil, tbrekke, tchandra, tserlin, xyu159
Target Milestone: z2   
Target Release: 3.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.8-106.el7cp Ubuntu: ceph_12.2.8-91redhat1 Doc Type: Bug Fix
Doc Text:
.The Ceph Object Gateway supports a string as a delimiter Invalid logic was used to find and project a delimiter sequence greater than one character. This was causing the Ceph Object Gateway to fail any request with a string as the delimiter, returning an `invalid utf-8 character` message. The logic handling the delimiter has been replaced by an 8-bit shift-carry equivalent. As a result, a string delimiter will work correctly. Red Hat has only tested this against the `US-ascii` character set.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-30 15:56:43 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: 1629656    

Description Vikhyat Umrao 2018-12-19 17:56:55 UTC 
Description of problem:
rgw does not support delimiter as a string it only supports a single character 
Upstream tracker - http://tracker.ceph.com/issues/24821


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

How reproducible:
Always
Comment 2 Vikhyat Umrao 2019-01-15 00:45:08 UTC 
*** Bug 1666086 has been marked as a duplicate of this bug. ***
Comment 12 errata-xmlrpc 2019-04-30 15:56:43 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-2019:0911