Bug 1224560

Summary: BootLoaderError: failed to write boot loader configuration
Product: [Fedora] Fedora Reporter: Martín Cigorraga <martincigorraga>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, ben.navetta, bugzilla, g.kaviyarasu, jonathan, ngompa13, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6a7e0c7daf466463642ed3657697e686ca258b210b9e03daee3864ec112033e6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:13:54 UTC Type: ---
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
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: program.log none

Description Martín Cigorraga 2015-05-24 16:53:59 UTC
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

Comment 1 Martín Cigorraga 2015-05-24 16:54:05 UTC
Created attachment 1029226 [details]
File: anaconda-tb

Comment 2 Martín Cigorraga 2015-05-24 16:54:07 UTC
Created attachment 1029227 [details]
File: anaconda.log

Comment 3 Martín Cigorraga 2015-05-24 16:54:08 UTC
Created attachment 1029228 [details]
File: environ

Comment 4 Martín Cigorraga 2015-05-24 16:54:10 UTC
Created attachment 1029229 [details]
File: lsblk_output

Comment 5 Martín Cigorraga 2015-05-24 16:54:11 UTC
Created attachment 1029230 [details]
File: nmcli_dev_list

Comment 6 Martín Cigorraga 2015-05-24 16:54:12 UTC
Created attachment 1029231 [details]
File: os_info

Comment 7 Martín Cigorraga 2015-05-24 16:54:16 UTC
Created attachment 1029232 [details]
File: storage.log

Comment 8 Martín Cigorraga 2015-05-24 16:54:18 UTC
Created attachment 1029233 [details]
File: syslog

Comment 9 Martín Cigorraga 2015-05-24 16:54:19 UTC
Created attachment 1029234 [details]
File: ifcfg.log

Comment 10 Martín Cigorraga 2015-05-24 16:54:21 UTC
Created attachment 1029235 [details]
File: program.log

Comment 11 Martín Cigorraga 2015-05-24 22:21:55 UTC
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

Comment 12 Neal Gompa 2015-08-05 11:53:49 UTC
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

Comment 13 Chris Murphy 2016-02-13 21:08:18 UTC
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.

Comment 14 Fedora End Of Life 2016-07-19 14:13:54 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.