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 2096900 - ReaR fails to regenerate initrd after restore
Summary: ReaR fails to regenerate initrd after restore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rear
Version: 9.0
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-14 14:09 UTC by Lukáš Zaoral
Modified: 2022-11-15 11:48 UTC (History)
2 users (show)

Fixed In Version: rear-2.6-12.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:42:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2825 0 None Merged Replace `mkinitrd` with `dracut` on Fedora and RHEL 2022-07-12 08:36:02 UTC
Red Hat Issue Tracker RHELPLAN-125233 0 None None None 2022-06-14 14:20:01 UTC
Red Hat Product Errata RHBA-2022:8246 0 None None None 2022-11-15 10:42:43 UTC

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


Note You need to log in before you can comment on or make changes to this bug.