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.

Description of problem:

The issue was reported Upstream through https://github.com/rear/rear/issues/2035
Depending on the LVM configuration, it may happen that rear recover seems to hang when rebuilding the initramfs. It's not hanging, but extremely slow.

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

rear-2.4-4


How reproducible:

Don't know exactly.

Hi Renaud, do you know what is the LVM configuration that causes this? I think QE will need to know this for testing.

Hi Pavel,

I don't know exactly but probably any LVM configuration causes this, as long as dracut must run in the chroot (this implies having different hardware or modules loaded).
Then if LVM configuration is large, this may be an issue.
This happens because LVM relies on udev to get device information (see "obtain_device_list_from_udev = 1" in /etc/lvm/lvm.conf).

Without the fix, due to not having /run/udev directory in the chroot, LVM waits for 10 seconds each time it tries to get a device.
See in particular Issue reported Upstream: https://github.com/rear/rear/issues/2035

Unfortunately I had no time testing this. This requires recovering a system of course.

Renaud.

Should I clone it to RHEL 8?

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-2020:1153