Created attachment 1016882 [details]
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
not checked yet
Steps to Reproduce:
1. install F22 in VM
2. boot to installed system
3. install F22 in same VM
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.
Created attachment 1016883 [details]
Created attachment 1016885 [details]
Created attachment 1016886 [details]
Created attachment 1016887 [details]
Created attachment 1016888 [details]
Created attachment 1016889 [details]
Created attachment 1016890 [details]
Created attachment 1016891 [details]
Created attachment 1016892 [details]
efibootmgr exited on SIGABRT
15:33:22,085 INFO program: Running... efibootmgr -b 0004 -B
15:33:22,362 DEBUG program: Return code: -6
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
Thank you for reporting this bug and we are sorry it could not be fixed.