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:
/CoreOS/rear/Regression/bz1672938-numerous-multipath-performance now fails.

When I extend the timeout, rear mkrescue in the test takes 4445s. In ReaR 2.4, it took 300s.

Version-Release number of selected component (if applicable):
2.6-1.el8

How reproducible:
easily, preferably on a machine with lots of RAM

Steps to Reproduce:
1. wow rhel-8.5 --reserve --arch x86_64  --taskparam=VERSIONLOCK=true --brew-build  rear-2.6-1.el8  --brew-method=multi /CoreOS/rear/Regression/bz1672938-numerous-multipath-performance

Actual results:
test fails

Expected results:
test should pass

Additional info:

this is due to this line https://github.com/rear/rear/pull/2299/files#diff-2916f533f1aa01a8a571a7062e43957bdd1523e70ce94a5107541ff466eef22cR705 
and the easiest fix is to comment it out, although it will reintroduce the problem that the line was supposed to fix - but we never had the fix anyway, so in RHEL it is not a regression.

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/RHEA-2021:4344