Bug 1379666

Summary:	grubx64.efi fails to boot with Secure Boot
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Installation	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	6.3.0	CC:	bbuckingham, lzap, stbenjam
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/16705
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:39:55 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:

Description Roman Plevka 2016-09-27 11:49:16 UTC

Description of problem:
I got to test the UEFI feature on a bare metal host (Dell PowerEdge R330) and found out, the /var/lib/tftpboot/grub2/grubx64.efi fails to boot with 'validation failed' [1] when Secure Boot is enabled.

On lzap's advice, i tried to replace the file by the one located in /boot/efi/EFI/redhat/grubx64.efi which booted just fine.

Is there a problem with signing the bootloader?

Version-Release number of selected component (if applicable):
6.3.0 Snap 1

How reproducible:


Steps to Reproduce:
1. get a machine supporting UEFI and secure boot
2. create a host with "Grub2 Uefi Secure Boot" pxe loader option

Actual results:
Verification failed:
http://storage2.static.itmages.com/i/16/0923/h_1474643658_3444841_50e85b6ce5.png


Expected results:
the signature is valid and secure boot allows the bootloader to boot

Additional info:

Comment 1 Roman Plevka 2016-09-27 11:58:55 UTC

Created redmine issue http://projects.theforeman.org/issues/16705 from this bug

Comment 3 Bryan Kearney 2016-09-27 14:20:52 UTC

Upstream bug component is Installer

Comment 6 Bryan Kearney 2016-10-12 10:15:49 UTC

Upstream bug assigned to lzap

Comment 11 Lukas Zapletal 2016-10-21 12:17:28 UTC

Shim is correctly deployed, the problem is we build our own grubx64.efi file during installation and apparently it is missing some bits (signature perhaps). The solution will be to copy pre-built version from /boot/EFI directory, which was confirmed to work.

Comment 14 Bryan Kearney 2016-11-24 11:16:15 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16705 has been resolved.

Comment 15 Roman Plevka 2017-10-26 15:10:08 UTC

VERIFIED
sat6.3.0-#20

the new grubx64.efi file gets loaded just fine and loads.

Comment 16 Bryan Kearney 2018-02-21 16:38:42 UTC

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/RHSA-2018:0336

Comment 17 Bryan Kearney 2018-02-21 16:39:55 UTC

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/RHSA-2018:0336

Comment 18 Satellite Program 2018-02-21 16:54:17 UTC

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/RHSA-2018:0336