Bug 1478584
| Summary: | Rear backup archive not getting included in the ISO for ppc64. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ryan Blakley <rblakley> |
| Component: | rear | Assignee: | Pavel Cahyna <pcahyna> |
| Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> |
| Severity: | high | Docs Contact: | Vladimír Slávik <vslavik> |
| Priority: | high | ||
| Version: | 6.9 | CC: | cww, jkurik, ovasik, pcahyna, rmetrich, tbowling, tcerna, vslavik |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-19 05:19:47 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1374441, 1461138, 1494482, 1494506 | ||
|
Description
Ryan Blakley
2017-08-04 21:09:08 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'
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 |