Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 1290929[details]
EFI shell screen shot with rescue ISO booting
Description of problem:
When Secureboot enabled at BIOS level, Rear Rescue ISO is not booting to do the recovery.
Version-Release number of selected component (if applicable):
Rear1.17.2-9.el7_3.x86_64
How reproducible:
Create a rescue ISO using "rear mkrescue" comamnd, when secureboot enabled at BIOS level. try to boot with that ISO to do the recovery.
Steps to Reproduce:
1.rear mkrescue
2.boot with the rescue ISO
Actual results:
rescue ISO is not bootable.
Expected results:
rescue ISO should be bootable.
Additional info:
Hi Pavel Cahyna,
you are correct,ReaR 2.2 and later supports secure boot.
In that case with RHEL 7.3 how we can use ReaR 2.2? with RHEL 7.3 distribution Rear1.17.2-9.el7_3.x86_64 is available. how we can get ReaR 2.2 with RHEL 7.3?
Thanks & Regards,
Jagan
(In reply to Jagan from comment #4)
> Hi Pavel Cahyna,
>
> you are correct,ReaR 2.2 and later supports secure boot.
>
> In that case with RHEL 7.3 how we can use ReaR 2.2? with RHEL 7.3
> distribution Rear1.17.2-9.el7_3.x86_64 is available. how we can get ReaR 2.2
> with RHEL 7.3?
>
> Thanks & Regards,
> Jagan
Hi jagan,
sorry for the late reply. We are considering updating ReaR to a newer version in the next RHEL 7 release, which should bring this functionality.
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-2018:3293
Created attachment 1290929 [details] EFI shell screen shot with rescue ISO booting Description of problem: When Secureboot enabled at BIOS level, Rear Rescue ISO is not booting to do the recovery. Version-Release number of selected component (if applicable): Rear1.17.2-9.el7_3.x86_64 How reproducible: Create a rescue ISO using "rear mkrescue" comamnd, when secureboot enabled at BIOS level. try to boot with that ISO to do the recovery. Steps to Reproduce: 1.rear mkrescue 2.boot with the rescue ISO Actual results: rescue ISO is not bootable. Expected results: rescue ISO should be bootable. Additional info: