Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1571266

Summary:	PPC64: cannot create DVD images including backup and cannot split DVD images
Product:	Red Hat Enterprise Linux 7	Reporter:	Renaud Métrich <rmetrich>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	medium	Docs Contact:	Marie Hornickova <mdolezel>
Priority:	urgent
Version:	7.5	CC:	djez, fkrska, ovasik, pcahyna, rmetrich, tbowling
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rear-2.4-1.el7	Doc Type:	Release Note
Doc Text:	Rear includes backup archive in the rescue CD ISO image 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. This update adds the backup archive into the rescue CD ISO image. As a result, rescue CDs can now be used to restore the system with internal backup method.	Story Points:	---
Clone Of:
Clones:	1596182 (view as bug list)		Environment:
Last Closed:	2018-10-30 11:43:19 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:	1596182

Description Renaud Métrich 2018-04-24 12:23:13 UTC

Description of problem:

It appears that there is no code in /usr/share/rear/output/ISO/Linux-ppc64le/ ana /usr/share/rear/output/ISO/Linux-ppc64/ to include the backup in the ISO, when using the following configuration:

OUTPUT=ISO
OUTPUT_URL=file:///home/backup/
BACKUP=NETFS
BACKUP_URL=iso:///OS

Also, the code used to split DVDs is not present.


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

rear-2.00


How reproducible:

Always


Steps to Reproduce:
1. Configure rear as shown above
2. Create backup: "rear mkbackup"
3. Check resulting ISO

Actual results:

No OS/backup.tar.gz file in the ISO


Additional info:

The code has been integrated into rear-2.2

Comment 3 Pavel Cahyna 2018-04-24 12:56:34 UTC

is it related to bz1478584 ?

Comment 4 Renaud Métrich 2018-04-24 13:23:05 UTC

It is, wasn't aware of

Comment 18 Pavel Cahyna 2018-06-27 16:22:58 UTC

merged upstream in 2.2/7124c122f855d83f0e7d373416ed95bc3d9e0cbb

Comment 25 errata-xmlrpc 2018-10-30 11:43:19 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:3293