Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionJoniel Pasqualetto
2020-08-21 19:22:14 UTC
Description of problem:
Currently, when using FDI, there is a single kexec command which is executed when foreman triggers the power/kexec api.
This single command only works in systems using BIOS or UEFI without SecureBoot.
It seems to be possible to kexec systems using UEFI + SecureBoot using the kexec option "-s".
Adding a condition that will check if the system is using SecureBoot and changing accordingly the kexec options to be used, would allow provisioning those systems using FDI.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Configure a VM or a physical machine to use UEFI + SecureBoot
2. Try provisioning using discovery method
Actual results:
kexec fails, in the discovered host, with error below and doesn't restart:
~~~
kexec_load failed: Operation not permitted
~~~
Expected results:
kexec load would work and start provisioning
Additional info:
There is a PR upstream. Will link the BZ to it.
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 (Moderate: Satellite 6.9 Release), 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/RHSA-2021:1313