This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1791608 - [RFE] Satellite should provide a feature to provision systems with UEFI Secure Boot enabled
Summary: [RFE] Satellite should provide a feature to provision systems with UEFI Secur...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-16 09:21 UTC by Stefan Meyer
Modified: 2024-06-06 06:15 UTC (History)
29 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:34:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-23374 0 None Migrated None 2024-06-06 06:15:24 UTC
Red Hat Issue Tracker SAT-2549 0 None None None 2024-06-03 16:25:09 UTC
Red Hat Knowledge Base (Solution) 4843841 0 None None None 2020-02-20 19:02:01 UTC

Comment 16 Lukas Zapletal 2021-08-12 10:28:20 UTC 
HTTP UEFI SecureBoot works, its just not supported or tested.

Just follow our HTTP UEFI chapter but instead "Grub2 UEFI HTTP" PXE loader, choose "Grub2 UEFI HTTP SecureBoot" option. This will make the DHCP server to reply with "shim.efi" filename option which then verifies the signature and passes over to grub2 signed by Red Hat keys.

Other workflows like Discovery or Bootdisk are not supported and will not work at the moment.

https://docs.theforeman.org/nightly/Provisioning_Guide/index-foreman-el.html#creating-hosts-with-uefi-http-boot-provisioning_provisioning
Comment 37 Mike McCune 2022-07-08 17:15:31 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 43 Jerone Young 2023-12-22 16:54:23 UTC 
Some work has started upstream in the fog-libvirt project. Once it can get accepted then it's a matter of how will Satellite expose it.

https://github.com/fog/fog-libvirt/issues/128
Comment 44 Eric Helms 2024-06-05 21:34:47 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 45 Christian Koep 2024-06-06 06:15:24 UTC 
https://issues.redhat.com/browse/SAT-2549
https://issues.redhat.com/browse/SAT-23374

In case anyone is wondering.
Note You need to log in before you can comment on or make changes to this bug.