Bug 1853098

Summary:	Bug allows ordered bucket listing to get stuck -- 5.0
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	J. Eric Ivancich <ivancich>
Component:	RGW	Assignee:	J. Eric Ivancich <ivancich>
Status:	CLOSED ERRATA	QA Contact:	Madhavi Kasturi <mkasturi>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.0	CC:	cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, sweil, tchandra, tserlin
Target Milestone:	---
Target Release:	5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-15.2.4-3.el8cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1853052	Environment:
Last Closed:	2021-08-30 08:25:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description J. Eric Ivancich 2020-07-02 00:23:06 UTC

+++ This bug was initially created as a clone of Bug #1853052 +++

Description of problem:

When a single call to an ordered bucket listing contains only common prefixes (i.e., delimiter is set), it's possible for the code to get stuck. 

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


How reproducible:

Very.

Steps to Reproduce:
1. Create a bucket in s3 that contains over 1000 entries with no "objects" at the top level and only "subdirectories".
2. Use s3cmd to list that bucket

Actual results:

No results provided; code is in infinite loop.

Expected results:

Listing produced.

Additional info:

See upstream tracker: https://tracker.ceph.com/issues/45955

--- Additional comment from RHEL Program Management on 2020-07-01 19:48:11 UTC ---

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

--- Additional comment from J. Eric Ivancich on 2020-07-01 19:50:20 UTC ---

The fix for this already exists and was intended for a code clean-up. But it also addresses this issue. The reason is subtle -- a logging message at level 20 was used to, as a side-effect, increment a loop control variable. But due to optimizations, the code (and side-effect) is never executed unless the logging level is 20 or above.

Comment 1 J. Eric Ivancich 2020-07-02 23:05:06 UTC

commit added to ceph-5.0-rhel-patches

Comment 8 errata-xmlrpc 2021-08-30 08:25:57 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 (Red Hat Ceph Storage 5.0 bug fix and enhancement), 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-2021:3294