Bug 1224560
Summary: | BootLoaderError: failed to write boot loader configuration | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martín Cigorraga <martincigorraga> | ||||||||||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 22 | CC: | 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
Martín Cigorraga
2015-05-24 16:53:59 UTC
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. |