Bug 2182690

Summary:	rrsync does not support --mkpath
Product:	Red Hat Enterprise Linux 9	Reporter:	mhuin
Component:	rsync	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED MIGRATED	QA Contact:	rhel-cs-infra-services-qe <rhel-cs-infra-services-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jorton, jwboyer
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 22:27:49 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 mhuin 2023-03-29 10:59:56 UTC

Description of problem:

the support script rrsync does not support the valid --mkpath option when invoking rsync.

This was fixed in https://github.com/WayneD/rsync/issues/200 in 2021. Since then several versions of rsync including that fix were released.

the c9s* branches use a very outdated version of rsync: https://git.centos.org/rpms/rsync/blob/c9-beta/f/SPECS/rsync.spec


Steps to Reproduce:
1. configure rrsync on the authorized_keys file of the target server
2. attempt to rsync with the --mkpath argument
3. rsync fails with a message: "rrsync: unsupported argument"

Expected results:

rsync should succeed

Comment 1 RHEL Program Management 2023-09-21 22:24:13 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 22:27:49 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.