Hide Forgot
Description of problem: Installing f25, btrfs with LUKS Version-Release number of selected component: anaconda-25.20.8-1 The following was filed automatically by anaconda: anaconda 25.20.8-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.5/site-packages/pyanaconda/bootloader.py", line 1579, in write_config raise BootLoaderError("failed to write boot loader configuration") File "/usr/lib64/python3.5/site-packages/pyanaconda/bootloader.py", line 1762, in write self.write_config() # pylint: disable=no-member File "/usr/lib64/python3.5/site-packages/pyanaconda/bootloader.py", line 2420, in writeBootLoaderFinal storage.bootloader.write() File "/usr/lib64/python3.5/site-packages/pyanaconda/bootloader.py", line 2447, in writeBootLoader writeBootLoaderFinal(storage, payload, instClass, ksdata) File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 252, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python3.5/threading.py", line 862, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self, *args, **kwargs) pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-Atomic-ostree-x86_64-25 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 25
Created attachment 1224675 [details] File: anaconda-tb
Created attachment 1224676 [details] File: anaconda.log
Created attachment 1224677 [details] File: environ
Created attachment 1224678 [details] File: lsblk_output
Created attachment 1224679 [details] File: nmcli_dev_list
Created attachment 1224680 [details] File: os_info
Created attachment 1224681 [details] File: storage.log
Created attachment 1224682 [details] File: syslog
Created attachment 1224683 [details] File: ifcfg.log
Created attachment 1224684 [details] File: program.log
Using Fedora-Atomic-ostree-x86_64-25-20161121.0.iso
Similar problem has been detected: Using the Fedora 25 Automic install .iso the instalation fails consistently when trying to write the bootloader. I have experienced this while attempting to install to two separate drives. The Fedora server installer succeeds. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-Atomic-ostree-x86_64-25 quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 package: anaconda-25.20.8-1 packaging.log: product: Fedora reason: pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 25
Only workaround was 1. Disconnect any drives which you do not need for the installation 2. Do not use EFI Then installation succeeded.
Similar problem has been detected: Wrote Fedora-Atomic-ostree-x86_64-25-20161205.0.iso onto USB media, booted using EFI and started the installation. Left pretty much everything at its default, except in the partitioning section I made additional space available and deleted all pre-existing partitions. I already tried the stable iso 20161121.0 with the same result. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-Atomic-ostree-x86_64-25 quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 package: anaconda-25.20.8-1 packaging.log: product: Fedora reason: pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 25
Similar problem has been detected: Same procedure as with Fedora-Atomic-ostree-x86_64-25-20161205.0.iso, only this time with the newest stable build 20161207.0. addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-Atomic-ostree-x86_64-25 quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 package: anaconda-25.20.8-1 packaging.log: product: Fedora reason: pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 25
Similar problem has been detected: installation of Fedora 25 Atomic Host ISO to Hyper-V virtual machine (Generation 2), where host in Windows 10 pro x64 addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-Atomic-ostree-x86_64-25 quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 package: anaconda-25.20.8-1 packaging.log: product: Fedora reason: pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 25
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.