Bug 1629514

Summary: pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration
Product: [Fedora] Fedora Reporter: Ritesh Khadgaray <khadgaray>
Component: anacondaAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: anaconda-maint-list, burni, jonathan, kellin, phildarocha, vanmeeuwen+fedora, vponcova, wwoods, youssef.m.sourani
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5a3ec568a2a688ed35d55f103a1015ad7396a2c14c1653cd16a0d1bdf42d7992;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 21:06:32 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: dbus.log
none
File: environ
none
File: lorax-packages.log
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log none

Description Ritesh Khadgaray 2018-09-17 02:22:26 UTC
Description of problem:
btrfs for root fs

Version-Release number of selected component:
anaconda-29.24.1

The following was filed automatically by anaconda:
anaconda 29.24.1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.7/site-packages/pyanaconda/bootloader.py", line 1629, in write_config
    raise BootLoaderError("failed to write boot loader configuration")
  File "/usr/lib64/python3.7/site-packages/pyanaconda/bootloader.py", line 1676, in write
    self.write_config()
  File "/usr/lib64/python3.7/site-packages/pyanaconda/bootloader.py", line 2519, in writeBootLoaderFinal
    storage.bootloader.write()
  File "/usr/lib64/python3.7/site-packages/pyanaconda/bootloader.py", line 2549, in writeBootLoader
    writeBootLoaderFinal(storage, payload, instClass, ksdata)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/installation_tasks.py", line 438, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/installation_tasks.py", line 472, in start
    self.run_task()
  File "/usr/lib64/python3.7/site-packages/pyanaconda/installation_tasks.py", line 304, in start
    item.start()
  File "/usr/lib64/python3.7/site-packages/pyanaconda/installation_tasks.py", line 304, in start
    item.start()
  File "/usr/lib64/python3.7/site-packages/pyanaconda/installation.py", line 375, in doInstall
    installation_queue.start()
  File "/usr/lib64/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/threading.py", line 286, in run
    threading.Thread.run(self)
pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration

Additional info:
addons:         com_redhat_kdump, com_redhat_docker
blivet-gui-utils.log: 
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-SB-ostree-x86_64-29 quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.18.5-300.fc29.x86_64
product:        Fedora
release:        Cannot get release name.
release_type:   pre-release
type:           anaconda
version:        29

Potential duplicate: bug 1566128

Comment 1 Ritesh Khadgaray 2018-09-17 02:22:33 UTC
Created attachment 1483818 [details]
File: anaconda-tb

Comment 2 Ritesh Khadgaray 2018-09-17 02:22:34 UTC
Created attachment 1483819 [details]
File: anaconda.log

Comment 3 Ritesh Khadgaray 2018-09-17 02:22:35 UTC
Created attachment 1483820 [details]
File: dbus.log

Comment 4 Ritesh Khadgaray 2018-09-17 02:22:37 UTC
Created attachment 1483821 [details]
File: environ

Comment 5 Ritesh Khadgaray 2018-09-17 02:22:39 UTC
Created attachment 1483822 [details]
File: lorax-packages.log

Comment 6 Ritesh Khadgaray 2018-09-17 02:22:40 UTC
Created attachment 1483823 [details]
File: lsblk_output

Comment 7 Ritesh Khadgaray 2018-09-17 02:22:41 UTC
Created attachment 1483824 [details]
File: nmcli_dev_list

Comment 8 Ritesh Khadgaray 2018-09-17 02:22:42 UTC
Created attachment 1483825 [details]
File: os_info

Comment 9 Ritesh Khadgaray 2018-09-17 02:22:43 UTC
Created attachment 1483826 [details]
File: program.log

Comment 10 Ritesh Khadgaray 2018-09-17 02:22:45 UTC
Created attachment 1483827 [details]
File: storage.log

Comment 11 Ritesh Khadgaray 2018-09-17 02:22:48 UTC
Created attachment 1483828 [details]
File: syslog

Comment 12 Ritesh Khadgaray 2018-09-17 02:22:49 UTC
Created attachment 1483829 [details]
File: ifcfg.log

Comment 13 Ritesh Khadgaray 2018-09-17 02:23:53 UTC
dup of bz#1289752 ?

Comment 14 Sebastian 2018-10-09 23:48:46 UTC
Similar problem has been detected:

Possible cause: /dev/sdc4. Or maybe because no swap was assigned by me. Or because i used a bios_boot partition on a 3TB GPT drive. That is all what may differ from other people's installations.

addons:         com_redhat_kdump, com_redhat_docker
blivet-gui-utils.log: 
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-SB-ostree-x86_64-29 rd.live.check quiet
hashmarkername: anaconda
kernel:         4.18.5-300.fc29.x86_64
package:        anaconda-29.24.3
packaging.log:  
product:        Fedora
reason:         pyanaconda.bootloader.BootLoaderError: failed to write boot loader configuration
release:        Cannot get release name.
release_type:   pre-release
version:        29

Comment 15 Sebastian 2018-10-12 12:39:46 UTC
I have installed the Fedora-AtomicWorkstation-ostree-x86_64-28.iso today, and the exact same problem with the bootloader persists. Out of frustration, i tested again with a Fedora-Live-Games-27.iso and that installation was successful, so i conclude this is not a problem with my hard drive.

Oh, and i burnt it on DVD and removed my USB-Bootdrive. So, /dev/sdc4 is out of the way.

Comment 16 Vendula Poncova 2018-11-01 11:05:34 UTC
From program.log:

22:10:19,952 INF program: Running in chroot '/mnt/sysimage/ostree/deploy/fedora-workstation/deploy/478cb224043d9f5175ba282ffc787350a9c6e1ff46411e0f19f262d60df97e93.0'... grub2-mkconfig -o /boot/grub2/grub.cfg
22:10:20,328 INF program: /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?).
22:10:20,345 DBG program: Return code: 1

However, I don't know what causes this problem. Reassigning to Colin Walters.

Comment 17 Ben Cotton 2019-10-31 19:57:16 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 18 Ben Cotton 2019-11-27 21:06:32 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.