Description of problem: After error "failed to write boot loader configuration" selected "no" 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 1820, in write self.write_config() # pylint: disable=no-member 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=/images/pxeboot/vmlinuz 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 1566123
Created attachment 1484081 [details] File: anaconda-tb
Created attachment 1484082 [details] File: anaconda.log
Created attachment 1484083 [details] File: dbus.log
Created attachment 1484084 [details] File: environ
Created attachment 1484085 [details] File: lorax-packages.log
Created attachment 1484086 [details] File: lsblk_output
Created attachment 1484087 [details] File: lvm.log
Created attachment 1484088 [details] File: nmcli_dev_list
Created attachment 1484089 [details] File: os_info
Created attachment 1484090 [details] File: program.log
Created attachment 1484091 [details] File: storage.log
Created attachment 1484092 [details] File: syslog
Created attachment 1484093 [details] File: ifcfg.log
From program.log: 10:43:04,012 INF program: Running in chroot '/mnt/sysimage/ostree/deploy/fedora-workstation/deploy/478cb224043d9f5175ba282ffc787350a9c6e1ff46411e0f19f262d60df97e93.0'... grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 10:43:05,180 INF program: /usr/bin/grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory. 10:43:05,181 INF program: /sbin/grub2-mkconfig: line 268: /boot/efi/EFI/fedora/grub.cfg.new: No such file or directory 10:43:05,181 DBG program: Return code: 1 Reassigning to grub2.
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.
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.