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 1478584 - Rear backup archive not getting included in the ISO for ppc64.
Summary: Rear backup archive not getting included in the ISO for ppc64.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rear
Version: 6.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
Vladimír Slávik
URL:
Whiteboard:
Depends On:
Blocks: 1374441 1461138 1494482 1494506
TreeView+ depends on / blocked
 
Reported: 2017-08-04 21:09 UTC by Ryan Blakley
Modified: 2021-03-11 15:32 UTC (History)
8 users (show)

Fixed In Version: rear-1.17.2-5.el6
Doc Type: No Doc Update
Doc Text:
Previously, Relax-and-Recover (ReaR) did not include the backup archive in the rescue CD ISO image when run on the IBM Power Systems architecture. As a consequence, rescue CDs could not be used for restoring the system when the internal backup method was used. The backup archive is now included in the ISO image and rescue CDs are usable.
Clone Of:
Environment:
Last Closed: 2018-06-19 05:19:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1571266 0 urgent CLOSED PPC64: cannot create DVD images including backup and cannot split DVD images 2021-06-10 15:57:34 UTC
Red Hat Product Errata RHBA-2018:1900 0 None None None 2018-06-19 05:19:57 UTC

Internal Links: 1571266

Description Ryan Blakley 2017-08-04 21:09:08 UTC 
Description of problem: Rear backup archive not getting included in the ISO for ppc64.


How reproducible: Every time.


Steps to Reproduce:
1. Running # rear -d -v mkbackup on a ppc64 server

Actual results:
[root@ibm-p710-01-vios-lp1 ~]# rear -d -v mkbackup
Relax-and-Recover 1.17.2 / Git
Using log file: /var/log/rear/rear-ibm-p710-01-vios-lp1.log
mkdir: created directory `/var/lib/rear/output'
Creating disk layout
Creating root filesystem layout
TIP: To login as root via ssh you need to set up /root/.ssh/authorized_keys or SSH_ROOT_PASSWORD in your configuration file
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
Encrypting disabled
Creating tar archive '/tmp/rear.FXp7zVpiggnIl05/tmp/isofs/var/rear-backups/backup.tar.gz'
Archived 696 MiB [avg 3210 KiB/sec]OK
Archived 696 MiB in 223 seconds [avg 3196 KiB/sec] <<<<<
Making ISO image
Wrote ISO Image /var/lib/rear/output/rear-ibm-p710-01-vios-lp1.iso (96M)<<<<<
Copying resulting files to file location
You should also rm -Rf /tmp/rear.FXp7zVpiggnIl05


Expected results:
[root@ibm-p710-01-vios-lp1 ~]# rear -d -v mkbackup
Relax-and-Recover 1.17.2 / Git
Using log file: /var/log/rear/rear-ibm-p710-01-vios-lp1.log
Creating disk layout
Creating root filesystem layout
TIP: To login as root via ssh you need to set up /root/.ssh/authorized_keys or SSH_ROOT_PASSWORD in your configuration file
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
Encrypting disabled
Creating tar archive '/tmp/rear.ZiqfunJzRDMjdGv/tmp/isofs/rear-backups/backup.tar.gz'
Archived 707 MiB [avg 3217 KiB/sec]OK
Archived 707 MiB in 226 seconds [avg 3203 KiB/sec] <<<<<
Making ISO image
Making ISO image
Wrote ISO image: /var/lib/rear/output/rear-ibm-p710-01-vios-lp1.iso (810M) <<<<<
Copying resulting files to file location
You should also rm -Rf /tmp/rear.ZiqfunJzRDMjdGv


Additional info:
The issue appears to be fixed upstream, bug https://github.com/rear/rear/issues/697, pull request https://github.com/rear/rear/pull/1383. I tested the fix on a ppc64 test server and it works, the output is above in the Expected results section. The scripts under /usr/share/rear/output/ISO/ for ppc64 wasn't including the /tmp/rear.*/tmp/isofs/ directory.
Comment 3 Tereza Cerna 2018-04-16 12:00:51 UTC 
===========================
Failed in:
    rear-1.17.2-5.el6.ppc64
===========================

No ISO file was created in new version of rear.

RECOVERED SYSTEM:
-----------------
# cat /etc/rear/local.conf 
OUTPUT=ISO
BACKUP=NETFS
BACKUP_URL=nfs://$IPADDR/mnt/rear/
GRUB_RESCUE=1

# rear -v -d mkrescue
Relax-and-Recover 1.17.2 / Git
Using log file: /var/log/rear/rear-ibm-js22-04.log
Creating disk layout
Creating root filesystem layout
Copying files and directories
Copying binaries and libraries
Copying kernel modules
Creating initramfs
Copying resulting files to nfs location
You should also rm -Rf /tmp/rear.YBhMR8Cx2pbwtTx

NFS SERVER:
-----------
# ls /mnt/rear/ibm-js22-04
README  rear.log  VERSION

# cat VERSION | grep Build
Build date: Mon, 16 Apr 2018 07:48:50 -0400

# ls /mnt/rear/ibm-js22-04/rear.log
...
2018-04-16 07:49:28.251641492 Including output/default/20_make_prefix_dir.sh
2018-04-16 07:49:28.267720710 Including output/default/25_create_lock.sh
2018-04-16 07:49:28.288581406 Including output/ISO/Linux-ppc64/30_create_yaboot.sh
mkdir: created directory `/tmp/rear.YBhMR8Cx2pbwtTx/tmp/ppc'
mkdir: created directory `/tmp/rear.YBhMR8Cx2pbwtTx/tmp/ppc/chrp'
`/usr/lib/yaboot/yaboot' -> `/tmp/rear.YBhMR8Cx2pbwtTx/tmp/ppc/chrp/yaboot'
mkdir: created directory `/tmp/rear.YBhMR8Cx2pbwtTx/tmp/etc'
2018-04-16 07:49:28.319462639 Including output/ISO/Linux-ppc64/80_create_isofs.sh
/usr/share/rear/output/ISO/Linux-ppc64/80_create_isofs.sh: line 1: ../Linux-ppc64le/80_create_isofs.sh: No such file or directory
2018-04-16 07:49:28.323333404 Including output/ISO/Linux-ppc64/81_prepare_multiple_iso.sh
/usr/share/rear/output/ISO/Linux-ppc64/81_prepare_multiple_iso.sh: line 1: ../Linux-i386/81_prepare_multiple_iso.sh: No such file or directory
2018-04-16 07:49:28.327209102 Including output/ISO/Linux-ppc64/82_create_iso_image.sh
/usr/share/rear/output/ISO/Linux-ppc64/82_create_iso_image.sh: line 1: ../Linux-ppc64le/82_create_iso_image.sh: No such file or directory
2018-04-16 07:49:28.331069220 Including output/default/94_grub2_rescue.sh
2018-04-16 07:49:28.336802964 Including output/default/94_grub_rescue.sh
2018-04-16 07:49:28.343138983 Could not find grub (legacy) binary.
2018-04-16 07:49:28.346367169 Including output/default/95_copy_result_files.sh
2018-04-16 07:49:28.357049532 Copying resulting files to nfs location
`/usr/share/rear/conf/templates/RESULT_usage_ISO.txt' -> `/tmp/rear.YBhMR8Cx2pbwtTx/outputfs/ibm-js22-04/README'
Comment 12 errata-xmlrpc 2018-06-19 05:19:47 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, 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-2018:1900
Note You need to log in before you can comment on or make changes to this bug.