Bug 1213890

Summary: Second installation in same VM has issues with boot loader installation
Product: [Fedora] Fedora Reporter: Marcin Juszkiewicz <mjuszkie>
Component: efibootmgrAssignee: Peter Jones <pjones>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, g.kaviyarasu, jonathan, pjones, surya_prabhakar, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:48:12 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:
Bug Depends On:    
Bug Blocks: 922257    
Attachments:
Description Flags
screenshot
none
anaconda.log
none
dnf.log
none
dnf.rpm.log
none
hawkey.log
none
ifcfg.log
none
packaging.log
none
program.log
none
storage.log
none
syslog none

Description Marcin Juszkiewicz 2015-04-21 13:41:54 UTC
Created attachment 1016882 [details]
screenshot

Description of problem:

Decided to test Fedora 22 Beta RC1 in VM. First installation went fine but as I wanted to test something I just rebooted and launched installation again.

Selected use full disk and enabled encryption, selected "minimal install" from closest mirror with proxy, set root password and user creation.

Installation was going fine and then stopped at boot loader configuration.

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

Fedora 22 Beta RC1 image for AArch64

How reproducible:

not checked yet

Steps to Reproduce:
1. install F22 in VM
2. boot to installed system
3. install F22 in same VM

Actual results:

15:33:21,480 INFO anaconda: Installing boot loader
15:33:21,481 INFO anaconda: boot loader stage1 target device is sda1
15:33:21,482 INFO anaconda: boot loader stage2 target device is sda2
15:33:21,700 DEBUG anaconda: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage object at 0x3ff74997550>
15:33:22,364 INFO anaconda: bootloader.py: used boot args: rd.lvm.lv=fedora-server/root rd.luks.uuid=luks-02a5cc30-d7a3-4cb2-bdcd-09238063f4b0 rd.lvm.lv=fedora-server/swap 
15:33:27,883 ERR anaconda: bootloader.write failed: failed to remove old efi boot entry.  This is most likely a kernel or firmware bug.


Expected results:

system boots

Additional info:

Comment 1 Marcin Juszkiewicz 2015-04-21 13:42:50 UTC
Created attachment 1016883 [details]
anaconda.log

Comment 2 Marcin Juszkiewicz 2015-04-21 13:43:14 UTC
Created attachment 1016885 [details]
dnf.log

Comment 3 Marcin Juszkiewicz 2015-04-21 13:44:23 UTC
Created attachment 1016886 [details]
dnf.rpm.log

Comment 4 Marcin Juszkiewicz 2015-04-21 13:46:17 UTC
Created attachment 1016887 [details]
hawkey.log

Comment 5 Marcin Juszkiewicz 2015-04-21 13:47:15 UTC
Created attachment 1016888 [details]
ifcfg.log

Comment 6 Marcin Juszkiewicz 2015-04-21 13:47:34 UTC
Created attachment 1016889 [details]
packaging.log

Comment 7 Marcin Juszkiewicz 2015-04-21 13:47:59 UTC
Created attachment 1016890 [details]
program.log

Comment 8 Marcin Juszkiewicz 2015-04-21 13:48:31 UTC
Created attachment 1016891 [details]
storage.log

Comment 9 Marcin Juszkiewicz 2015-04-21 13:49:13 UTC
Created attachment 1016892 [details]
syslog

Comment 10 David Shea 2015-04-21 13:54:25 UTC
efibootmgr exited on SIGABRT

15:33:22,085 INFO program: Running... efibootmgr -b 0004 -B
15:33:22,362 DEBUG program: Return code: -6

Comment 11 Fedora End Of Life 2016-07-19 13:48:12 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.