I think this is expected. ReaR makes the decision of which tools to include on the recovery image based on what it founds in the system. So if no UEFI found, no UEFI packages are included.

This could be changed by including them always (and depending on the appropriate packages, which would solve bz1492177 as well), but I am not sure how it would work anyway - UEFI needs a special partition AFAIK, so it is not a task of restoring a system into exactly the same state anymore but transforming it into a different state (partition layout will be different) and I would say this is out of scope.

Gratien, what do you think? Do you have plans for something like this?

I made an issue of this enhancement request as https://github.com/rear/rear/issues/1601
However, we can promise this will be implemented. OTOH, I like the idea of a  dual boot ISO. We will see what the other developers think of the idea.

(In reply to Gratien D'haese from comment #4)
> I made an issue of this enhancement request as
> https://github.com/rear/rear/issues/1601
> However, we can promise this will be implemented. OTOH, I like the idea of a
> dual boot ISO. We will see what the other developers think of the idea.

Thank you for your fast reply. But what about the partition layout? I am afraid that to make a properly functioning UEFI system one needs more than to make a bootable ISO.

(In reply to Pavel Cahyna from comment #5)
> 
> Thank you for your fast reply. But what about the partition layout? I am
> afraid that to make a properly functioning UEFI system one needs more than
> to make a bootable ISO.

Of course, and that counts for both ways. The repartitioning part (and resizing) is the most difficult part, but nothing is impossible. Cloning to another boot technology bring new challenges to say at least.

(In reply to Gratien D'haese from comment #6)
> (In reply to Pavel Cahyna from comment #5)
> > 
> > Thank you for your fast reply. But what about the partition layout? I am
> > afraid that to make a properly functioning UEFI system one needs more than
> > to make a bootable ISO.
> 
> Of course, and that counts for both ways. The repartitioning part (and
> resizing) is the most difficult part, but nothing is impossible. Cloning to
> another boot technology bring new challenges to say at least.

Repartitioning should not be a big issue, there is already code for that.
The difficult part here is to install the new bootloader on the disk after restoring the backup.
This would require installing missing efi packages based on distro, which may not be an easy task, typically depending on the network configuration (are repos accessible from inside the chroot, the configured network, etc?).

Anyway, this also requires implementing a failsafe manual method just saying "enter the /mnt/local chroot and install all that is missing manually".

Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days