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.

Created attachment 1918618 [details]
output from install.

Description of problem:
On recovery I am receiving 
"No filesystem mounted on '/mnt/local'. Stopping."


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

How reproducible:
100% on RHEL 9 and 8.6.

Steps to Reproduce:
1. use preprepared iso at https://people.redhat.com/~jkreft/rhel-discovery-iso.tar.gz
2. attempt rear recovery
3. see error message.

Actual results:
remediations from are not working
https://access.redhat.com/solutions/3295341

Expected results:
Install of the recovery system


Additional info:

Also referring to the following KCS articles

https://access.redhat.com/solutions/2115051

https://access.redhat.com/articles/5693681
Note that ^ article is the one being impacted 
We use an old version of the iso prepared for Discovery, but since updating it to the iso link provided we are running into these errors

Hello Justin, can you please provide the log ( /var/log/rear/rear-localhost.log )?

Let's get this done

Closing as this is not a problem in ReaR itself, but the interaction of the cloning procedure used to create the VM with LVM default settings (introduced in RHEL 9).

Recreating the installation using ReaR recovery will lead to the same problem as VM cloning, so a workaround in ReaR is needed to prevent this from happening (the workaround would not help with the problem reported here, because ReaR encounters a LVM setup that is already broken, one needs a workaround in the cloning procedure, for example by using virt-sysprep). This problem is tracked in bz2145014.