Bug 2172602

Summary:	ReaR is missing a dependency on s390utils on IBM Z
Product:	Red Hat Enterprise Linux 8	Reporter:	Pavel Cahyna <pcahyna>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	djez, ovasik, pcahyna, rhel-cs-system-management-subsystem-qe
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	s390x
OS:	Unspecified
Whiteboard:
Fixed In Version:	rear-2.6-9.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2172599	Environment:
Last Closed:	2023-05-16 08:42:15 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:	2172599
Bug Blocks:	2130206

Description Pavel Cahyna 2023-02-22 16:32:47 UTC

+++ This bug was initially created as a clone of Bug #2172599 +++

Description of problem:
If tools like lsdasd, dasdview, dasdinfo and many others (available in the s390utils package) are not installed, ReaR will create a rescue image, but the disk layout information will be wrong. The image will also lack these tools, thus it will be unusable for restoring.

How reproducible:
easily

Steps to Reproduce:
1. Install ReaR on a machine without s390utils (and s390utils-base, s390utils-core)
2. Run "rear savelayout"
3. Examine the resulting /var/lib/rear/layout/disklayout.conf

Actual results:
some entries are wrong, e.g. dasd_channel lines are missing parameters

Expected results:
rear should bring in the required utilities automatically and in the disklayout.conf file the dasd_channel lines have arguments like 0.0.0120

Additional info:
The s390utils package is actually a metapackage that depends on many other packages. The required tools are in the s390utils-base and s390utils-core packages, so one may add dependencies just on those.

Comment 8 errata-xmlrpc 2023-05-16 08:42:15 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-2023:2900