RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
rsync-out dose not support wildcard, if customer want to use the wildcard, need use "glob rsync-out".
Now, Can not find this help in rsync-out helpout, need update it.


Version-Release number of selected component (if applicable):
libguestfs-1.22.6-4.el7.x86_64


How reproducible:
Always


Steps to Reproduce:
Step 1:
# cat /tmp/rsyncd.conf
port = 33335
pid file = rsyncd.pid
[src]
path = /tmp/hostsrc
comment = source
use chroot = false
read only = true
[dest]
path = /tmp/hostdest
comment = destination
use chroot = false
read only = false

Step 2:
# rsync --daemon --config=/tmp/rsyncd.conf

Step 3:
# guestfish --network -a test1.img -m /dev/sda1
><fs> touch /test.c

><fs> rsync-out /*.c rsync://root.85.205:33335/dest/ archive:true
libguestfs: error: rsync_out: '/*.c' to 'rsync://root.85.205:33335/dest/': rsync: link_stat "/sysroot/*.c" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1039) [sender=3.0.6]

><fs> glob rsync-out /*.c rsync://root.85.205:33335/dest/ archive:true


Actual results:


Expected results:


Additional info:
Has same issue in RHEL, libguestfs-1.20.10-3.el6.x86_64

https://github.com/libguestfs/libguestfs/commit/c04fbbda3e1d2bf98e241a95e069ac1fe202c14f

Fix also included in libguestfs-1.20.10-4.el6 (note
there is no separate bug for RHEL 6, I just included
the fix in the routine build).

Verified with libguestfs-1.22.6-16.el7.x86_64

><fs> help rsync-out
    ...

    Globbing does not happen on the "src" parameter. In programs which use
    the API directly you have to expand wildcards yourself (see
    "glob_expand"). In guestfish you can use the "glob" command (see "glob"
    in guestfish(1)), for example:

     ><fs> glob rsync-out /* rsync://remote/


Help out is update.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.