Bug 1697815

Summary:	rear recover hangs when rebuilding the initramfs
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:
Priority:	medium
Version:	7.6	CC:	djez, pcahyna
Target Milestone:	rc
Target Release:	7.8
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rear-2.4-10.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1757488 (view as bug list)		Environment:
Last Closed:	2020-03-31 20:06:59 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:	1757488

Description Renaud Métrich 2019-04-09 07:29:14 UTC

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.

Comment 3 Pavel Cahyna 2019-08-22 16:52:16 UTC

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

Comment 4 Renaud Métrich 2019-08-23 09:33:17 UTC

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.

Comment 6 Pavel Cahyna 2019-09-05 14:52:26 UTC

Should I clone it to RHEL 8?

Comment 10 errata-xmlrpc 2020-03-31 20:06:59 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-2020:1153