Bug 2232161 - unicode decode errors break librados object iteration
Summary: unicode decode errors break librados object iteration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 6.0
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: 6.1z7
Assignee: Patrick Donnelly
QA Contact: Hemanth Kumar
Rivka Pollack
URL:
Whiteboard:
Depends On: 2232153
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-15 16:10 UTC by Patrick Donnelly
Modified: 2024-08-28 17:57 UTC (History)
4 users (show)

Fixed In Version: ceph-17.2.6-227.el9cp
Doc Type: Enhancement
Doc Text:
.The Python librados supports iterating object omap key/values Previously, the iteration would break whenever a binary/unicode key was encountered. With this release, the Python librados supports iterating object omap key/values with unicode or binary keys and the iteration continues as expected.
Clone Of:
Environment:
Last Closed: 2024-08-28 17:57:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 59716 0 None None None 2023-08-15 16:10:21 UTC
Red Hat Issue Tracker RHCEPH-7217 0 None None None 2023-08-15 16:29:05 UTC
Red Hat Product Errata RHBA-2024:5960 0 None None None 2024-08-28 17:57:31 UTC

Description Patrick Donnelly 2023-08-15 16:10:21 UTC
This bug was initially created as a copy of Bug #2232153

I am copying this bug because: 

6.X backport

Description of problem:

See: https://tracker.ceph.com/issues/59716

Comment 11 errata-xmlrpc 2024-08-28 17:57:28 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 6.1 security, bug fix, and enhancement updates.), 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-2024:5960


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