Bug 1262071

Summary: EFI boot entry installation fails
Product: [Fedora] Fedora Reporter: A.J. Werkman <aj.werkman>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-10 18:45:49 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:
Attachments:
Description Flags
Program.log
none
Anaconda.log
none
Dnf.repo.log none

Description A.J. Werkman 2015-09-10 18:41:44 UTC
Created attachment 1072320 [details]
Program.log

Description of problem:
When installing F23Beta_TC4 a screen pops up saying EFI boot entry might not be installed properly.

Version-Release number of selected component (if applicable):
F 23 Beta TC4

How reproducible:
Everytime

Steps to Reproduce:
1. Install a Fedora with simple choices.
2. Pop up says there is an installion problem with the EFI boot entry.
3. On reboot there is no boot entry for Fedora

Actual results:
No EFI boot entry

Expected results:
Boot entry should be in EFI to boot Fedora

Additional info:
When inspecting the log files on tty2 I see the efibootmgr command 'efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \EFI\fedora\shim.efi' that failed. When manually typing it again, the command succeeds and a Fedora EFI entry is created.

Comment 1 A.J. Werkman 2015-09-10 18:44:23 UTC
Created attachment 1072321 [details]
Anaconda.log

Comment 2 A.J. Werkman 2015-09-10 18:45:13 UTC
Created attachment 1072322 [details]
Dnf.repo.log

Comment 3 David Shea 2015-09-10 18:45:49 UTC

*** This bug has been marked as a duplicate of bug 1260799 ***