Description of problem: Trying to install bare-metal F22 Cloud-Atomic TC3 image, Anaconda crashes with the legend: "Failed to write boot information - System will not boot" (more or less...) Version-Release number of selected component: anaconda-22.20.12-1 The following was filed automatically by anaconda: anaconda 22.20.12-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1582, in write_config raise BootLoaderError("failed to write boot loader configuration") File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1629, in write self.write_config() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2372, in writeBootLoaderFinal storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2399, in writeBootLoader writeBootLoaderFinal(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 266, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, *args, **kwargs) BootLoaderError: failed to write boot loader configuration Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.1-300.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1029226 [details] File: anaconda-tb
Created attachment 1029227 [details] File: anaconda.log
Created attachment 1029228 [details] File: environ
Created attachment 1029229 [details] File: lsblk_output
Created attachment 1029230 [details] File: nmcli_dev_list
Created attachment 1029231 [details] File: os_info
Created attachment 1029232 [details] File: storage.log
Created attachment 1029233 [details] File: syslog
Created attachment 1029234 [details] File: ifcfg.log
Created attachment 1029235 [details] File: program.log
Another user experienced a similar problem: With Fedora-Cloud_Atomic-22-x86_64 from 2015-05-19, sha256: d46091cb5...blahblah...aad420b09 /boot ext4, 250mb swap, 2gb / btrfs, ~290gb Installing from an USB pendrive addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet hashmarkername: anaconda kernel: 4.0.2-300.fc22.x86_64 package: anaconda-22.20.13-1 packaging.log: product: Fedora reason: BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 22
Another user experienced a similar problem: I ran through the Fedora 22 Atomic Host ISO installer on VMware Fusion. addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22-x86_64 quiet hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 package: anaconda-22.20.13-1 packaging.log: product: Fedora reason: BootLoaderError: failed to write boot loader configuration release: Cannot get release name. version: 22
Prior to the crash, which doesn't happen in anaconda-23, is bug 1289752. The combination of Btrfs and ostree appears to confuse grub2-mkconfig.
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.