Bug 2096900

Summary:	ReaR fails to regenerate initrd after restore
Product:	Red Hat Enterprise Linux 9	Reporter:	Lukáš Zaoral <lzaoral>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	djez, pcahyna
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	rear-2.6-12.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 10:42:27 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:

Description Lukáš Zaoral 2022-06-14 14:09:22 UTC

Description of problem: ReaR fails to regenerate initrd after restore which may result in an unbootable system.

Version-Release number of selected component (if applicable): rear-2.6-11.el9

How reproducible: always

Steps to Reproduce:
1. Create a rescue image and backup of any type (ISO, USB, PXE, IPL, ...) using `rear mkbackup`.
2. Boot into such rescue system.
2. Run `rear recover` and answer all questions with affirmative replies.

Actual results:
The initrd is not regenerated.

Expected results:
The initrd is regenerated successfully after restore.

Additional info:
- Corresponding logs:
>Running mkinitrd...
>WARNING:
>Cannot create initrd (found no mkinitrd in the recreated system).
>Check the recreated system (mounted at /mnt/local)
>and decide yourself, whether the system will boot or not.

- The `mkinitrd` binary was removed in dracut 054 so it is no longer being shipped in RHEL 9:
  https://github.com/redhat-plumbers/dracut-rhel9/commit/43df4ee274e7135aff87868bf3bf2fbab47aa8b4

Comment 1 Lukáš Zaoral 2022-07-12 08:36:03 UTC

upstream PR with a fix: https://github.com/rear/rear/pull/2825

Comment 12 errata-xmlrpc 2022-11-15 10:42:27 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:8246