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.
Bug 2115918 - rsync OUTPUT_URL not respected when OUTPUT=PXE BACKUP=RSYNC
Summary: rsync OUTPUT_URL not respected when OUTPUT=PXE BACKUP=RSYNC
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.7
Assignee: Pavel Cahyna
QA Contact: David Jež
Šárka Jana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-05 17:15 UTC by Pavel Cahyna
Modified: 2022-11-08 11:09 UTC (History)
2 users (show)

Fixed In Version: rear-2.6-6.el8
Doc Type: Bug Fix
Doc Text:
.ReaR with the PXE output method no longer fails to store the output files in the rsync `OUTPUT_URL` location In RHEL 8.5, the handling of the `OUTPUT_URL` variable with the `OUTPUT=PXE` and `BACKUP=RSYNC` options was removed. As a consequence, when using an rsync location for `OUTPUT_URL`, ReaR failed to copy the `initrd` and kernel files to this location, although it uploaded them to the location specified by `BACKUP_URL`. With this update, the behavior from RHEL 8.4 and earlier releases is restored. ReaR creates the required files at the designated `OUTPUT_URL` destination using rsync.
Clone Of:
Environment:
Last Closed: 2022-11-08 10:02:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear issues 2781 0 None closed Missing /usr/share/rear/output/PXE/default/820_copy_to_net.sh and PXE output fails with rsync protocol - DRLM issue 189 2022-08-05 17:15:35 UTC
Red Hat Issue Tracker RHELPLAN-130415 0 None None None 2022-08-05 17:16:43 UTC
Red Hat Product Errata RHBA-2022:7654 0 None None None 2022-11-08 10:02:50 UTC

Description Pavel Cahyna 2022-08-05 17:15:35 UTC
Description of problem:

With the fix of bz1930662 (backport of https://github.com/rear/rear/pull/2632) the file /usr/share/rear/output/PXE/default/820_copy_to_net.sh was removed because it duplicated the generic code in output/default/950_copy_result_files.sh and output/RSYNC/default/900_copy_result_files.sh. Its treatment of OUTPUT_URL was different though: output/RSYNC/default/900_copy_result_files.sh copies the output files (kernel+initrd) to BACKUP_URL and ignores OUTPUT_URL. In contrast, 820_copy_to_net.sh passes $OUTPUT_URL directly to rsync. As a result of its removal, the files are not at the place where the user expects them. This is a problem for DRLM, which configures ReaR this way: https://github.com/rear/rear/issues/2781

Without OUTPUT=PXE and with BACKUP=RSYNC, OUTPUT_URL is also ignored, but this has been always the case, so it is not a regression and I don't propose to fix it here (only in RHEL 9 with a more invasive change, bz2115958)

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

2.4-19.el8

How reproducible:

mkrescue with appropriate settings is enough

Steps to Reproduce:
1. set BACKUP=RSYNC OUTPUT=PXE OUTPUT_URL=user@host:/path/rsync/output OUTPUT_URL=user@host:/path/rsync/backup
2. run rear mkrescue

Actual results:

The output files $(hostname -s).kernel and $(hostname -s).initrd.cgz are not found under /path/rsync/output on host (but they are under /path/rsync/backup)

Expected results:

The output files $(hostname -s).kernel and $(hostname -s).initrd.cgz are found under /path/rsync/output on host

Additional info:

OUTPUT_URL is used in an odd way here. Normally, ReaR uses its own rsync URL format (calling it "new style format"):

# rsync://[USER@]HOST[:PORT]/PATH    # using ssh
# rsync://[USER@]HOST[:PORT]::/PATH  # using rsync

but output/PXE/default/820_copy_to_net.sh passes the URL directly to rsync, which interprets it this way (ReaR calls it "old style format") :

# [USER@]HOST:PATH           # using ssh (no rsh)
#
# with rsync protocol PATH is a MODULE name defined in remote /etc/rsyncd.conf file
# [USER@]HOST::PATH          # using rsync
# rsync://[USER@]HOST[:PORT]/PATH    # using rsync (is not compatible with new style!!!)

This is different from the rest of ReaR, but should not be changed due to compatibility reasons: rsync://[USER@]HOST[:PORT]/PATH means using the rsync protocol (rsyncd) in the old style format, but ssh transport in the new style format. I plan to change it in RHEL 9, bz2115958

Comment 10 errata-xmlrpc 2022-11-08 10:02:43 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 (rear bug fix and enhancement 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/RHBA-2022:7654


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