Bug 1791608

Summary:	[RFE] Satellite should provide a feature to provision systems with UEFI Secure Boot enabled
Product:	Red Hat Satellite	Reporter:	Stefan Meyer <smeyer>
Component:	Provisioning	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.6.0	CC:	aganbat, ahumbe, alex.wang, bkearney, bsmitley, ckoep, cylopez, fgarciad, inecas, j.becker, kurathod, ldelouw, lstejska, lzap, mhulan, mschindl, rgreene, rheron, sadas, satellite6-bugs, saydas, sganar, sokeeffe, spurrier, sshtein, thadzhie
Target Milestone:	Unspecified	Keywords:	FutureFeature, PrioBumpGSS, Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-02 15:19:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.