Bug #16705
closed
grubx64.efi fails to boot with Secure Boot
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1379666
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:
Updated by Dominic Cleal about 8 years ago
- Project changed from Foreman to Installer
- Category set to Foreman modules
Updated by Lukas Zapletal about 8 years ago
- Priority changed from Normal to Urgent
Updated by Lukas Zapletal about 8 years ago
- Related to Feature #12635: Options to deploy Grub and PXELinux EFI loaders in TFTP root added
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/311 added
Updated by 
Updated by Lukas Zapletal almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-foreman_proxy|3c11b38f76680f9363971b490cbc6cf2838a7aab.
Updated by Dominic Cleal almost 8 years ago
- Translation missing: en.field_release set to 189