Bug 2249068

Summary:	rgw: cloud-sync: take upstream changes to permit sync of (virtual) folders
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Matt Benjamin (redhat) <mbenjamin>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	akraj, ceph-eng-bugs, cephqe-warriors, tserlin
Target Milestone:	---
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-18.2.1-95.el9cp	Doc Type:	Bug Fix
Doc Text:	.Sending workloads with embedded backslash (/) in object names to cloud-sync no longer causes sync failures Previously, incorrect URL-escaping of object paths during cloud sync caused sync failures when workloads contained objects with an embedded backslash (/) in the names, that is, when virtual directory paths were used. With this fix, incorrect escaping is corrected and workloads with embedded backslash (/) in object names can be sent to cloud-sync as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-13 14:23:09 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:

Description Matt Benjamin (redhat) 2023-11-10 14:13:24 UTC

Description of problem:

From upstream tracker:
"The logs showed that the requests being made to the primary rados gateway instance, included an object path, where the slash was being escaped into %2F. This resulted in a 404 error which bubbled up into an ENOENT error in the cloud sync module."

Comment 5 errata-xmlrpc 2024-06-13 14:23:09 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 (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and bug fix update), 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-2024:3925