RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1202320 - [atomic] BootLoaderError: failed to write bootloader configuration
Summary: [atomic] BootLoaderError: failed to write bootloader configuration
Keywords:
Status: CLOSED DUPLICATE of bug 1267860
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.1
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Radek Vykydal
QA Contact: Release Test Team
URL:
Whiteboard: abrt_hash:2d4428cfd3000eed227c719ab6f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-16 11:50 UTC by Alexander Todorov
Modified: 2015-10-01 18:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-01 18:50:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
File: anaconda-tb (334.98 KB, text/plain)
2015-03-16 11:50 UTC, Alexander Todorov 		no flags Details
File: anaconda.log (29.89 KB, text/plain)
2015-03-16 11:50 UTC, Alexander Todorov 		no flags Details
File: environ (404 bytes, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: lsblk_output (1.74 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: nmcli_dev_list (1.53 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: os_info (510 bytes, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: program.log (36.21 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: storage.log (146.64 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: syslog (70.68 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
File: ifcfg.log (1.27 KB, text/plain)
2015-03-16 11:51 UTC, Alexander Todorov 		no flags Details
1) atomic installer reproducer (4.04 KB, text/plain)
2015-07-16 10:26 UTC, Radek Vykydal 		no flags Details
2) reproducer with rhel installer (4.25 KB, text/plain)
2015-07-16 10:29 UTC, Radek Vykydal 		no flags Details
2) reproducer with rhel installer (729 bytes, text/plain)
2015-07-16 10:34 UTC, Radek Vykydal 		no flags Details
3) default lvm configuration with atomic installer (4.25 KB, text/plain)
2015-07-16 10:35 UTC, Radek Vykydal 		no flags Details
Show Obsolete (1) View All

Description Alexander Todorov 2015-03-16 11:50:56 UTC 
Version-Release number of selected component:
anaconda-19.31.79-1

The following was filed automatically by anaconda:
anaconda 19.31.79-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1570, in write_config
    raise BootLoaderError("failed to write bootloader configuration")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1609, in write
    self.write_config()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2376, in writeBootLoaderFinal
    storage.bootloader.write()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2403, in writeBootLoader
    writeBootLoaderFinal(storage, payload, instClass, ksdata)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 204, in doInstall
    writeBootLoader(storage, payload, instClass, ksdata)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 211, in run
    threading.Thread.run(self, *args, **kwargs)
BootLoaderError: failed to write bootloader configuration

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   method=http://download.eng.bos.redhat.com/rel-eng/Atomic/7/trees/GA.brew/images/20150217.0/installer/ fips=1
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.10.0-229.el7.x86_64
product:        Red Hat Enterprise Linux 7"
release:        Red Hat Enterprise Linux ComputeNode release 7.1 (Maipo)
type:           anaconda
version:        Red Hat Enterprise Linux ComputeNode"
Comment 1 Alexander Todorov 2015-03-16 11:50:58 UTC 
Created attachment 1002216 [details]
File: anaconda-tb
Comment 2 Alexander Todorov 2015-03-16 11:50:59 UTC 
Created attachment 1002217 [details]
File: anaconda.log
Comment 3 Alexander Todorov 2015-03-16 11:51:00 UTC 
Created attachment 1002218 [details]
File: environ
Comment 4 Alexander Todorov 2015-03-16 11:51:01 UTC 
Created attachment 1002219 [details]
File: lsblk_output
Comment 5 Alexander Todorov 2015-03-16 11:51:02 UTC 
Created attachment 1002220 [details]
File: nmcli_dev_list
Comment 6 Alexander Todorov 2015-03-16 11:51:03 UTC 
Created attachment 1002221 [details]
File: os_info
Comment 7 Alexander Todorov 2015-03-16 11:51:04 UTC 
Created attachment 1002222 [details]
File: program.log
Comment 8 Alexander Todorov 2015-03-16 11:51:05 UTC 
Created attachment 1002223 [details]
File: storage.log
Comment 9 Alexander Todorov 2015-03-16 11:51:06 UTC 
Created attachment 1002224 [details]
File: syslog
Comment 10 Alexander Todorov 2015-03-16 11:51:07 UTC 
Created attachment 1002225 [details]
File: ifcfg.log
Comment 11 Alexander Todorov 2015-03-16 11:53:59 UTC 
I'm not exactly sure what caused this problem. Initially I've had some partitions on disk which I managed to delete and created the default LVM configuration. Then I've changed the root mount point from LVM to BTRFS, IIRC and proceeded with the install. At the end of the installation I got this traceback. 


Before going into the installation UI I've also zeroed out the 1st MB of the vda disk using dd.
Comment 12 Brian Lane 2015-03-18 23:52:10 UTC 
10:44:05,800 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg
10:44:05,840 INFO program: /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?).

Looks like it doesn't like the btrfs / for some reason.
Comment 13 Radek Vykydal 2015-07-15 13:31:19 UTC 
I doubt this bug should be on InstallPrio list.
Colin, is / on btrfs something we should care about much for Atomic?
Comment 14 Colin Walters 2015-07-15 13:49:57 UTC 
(In reply to Radek Vykydal from comment #13)
> I doubt this bug should be on InstallPrio list.
> Colin, is / on btrfs something we should care about much for Atomic?

Well...btrfs has nicer management than the LVM stack in some cases, so I can imagine some people wanting to use it.

But long term I think for Atomic Host/docker, overlayfs is a primary focus.

It's OK by me if we just leave this bug open, it's not a priority indeed right now.
Comment 15 Radek Vykydal 2015-07-16 10:14:54 UTC 
The reproducer is to create default partitioning in custom partitioning spoke and change '/' to BTRFS.

grub2-probe fails to find device '/' is mounted on. I'll post /proc/self/mountinfo of 

1) reproducer with atomic installer - fails with the traceback
2) reproducer with rhel installer - doesn't traceback
3) default lvm configuration with atomic installer - doesn't traceback, not sure why

The root cause seems to be that grub2-probe in 1) is run in ostree deployment chroot, where physical target root device (the one probe is looking for?) is mounted to /sysroot whereas the probe looks for / and nothing is actually mounted to / in the chroot at the time of grub2-probe (<- grub2-mkconfig <- bootloader.write_config() <- writeBootLoader())? 

See the mounting before writeBootLoader

https://github.com/rhinstaller/anaconda/blob/atomic-rhel-7.1/pyanaconda/install.py#L175
Comment 16 Radek Vykydal 2015-07-16 10:26:38 UTC 
Created attachment 1052633 [details]
1) atomic installer reproducer

# /usr/sbin/grub2-probe -v --target=device /
(run in deployment chroot)

/usr/sbin/grub2-probe: info: adding `hd0' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: adding `hd1' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: changing current directory to /dev.
/usr/sbin/grub2-probe: info: changing current directory to rah.
/usr/sbin/grub2-probe: info: changing current directory to virtio-ports.
/usr/sbin/grub2-probe: info: changing current directory to snd.
/usr/sbin/grub2-probe: info: changing current directory to vfio.
/usr/sbin/grub2-probe: info: changing current directory to mqueue.
/usr/sbin/grub2-probe: info: changing current directory to hugepages.
/usr/sbin/grub2-probe: info: changing current directory to bsg.
/usr/sbin/grub2-probe: info: changing current directory to disk.
/usr/sbin/grub2-probe: info: changing current directory to by-label.
/usr/sbin/grub2-probe: info: changing current directory to by-uuid.
/usr/sbin/grub2-probe: info: changing current directory to by-id.
/usr/sbin/grub2-probe: info: changing current directory to block.
/usr/sbin/grub2-probe: info: changing current directory to char.
/usr/sbin/grub2-probe: info: changing current directory to net.
/usr/sbin/grub2-probe: info: changing current directory to mapper.
/usr/sbin/grub2-probe: info: changing current directory to pts.
/usr/sbin/grub2-probe: info: changing current directory to shm.
/usr/sbin/grub2-probe: info: changing current directory to input.
/usr/sbin/grub2-probe: info: changing current directory to by-path.
/usr/sbin/grub2-probe: info: changing current directory to by-id.
/usr/sbin/grub2-probe: info: changing current directory to bus.
/usr/sbin/grub2-probe: info: changing current directory to usb.
/usr/sbin/grub2-probe: info: changing current directory to 001.
/usr/sbin/grub2-probe: info: changing current directory to raw.
/usr/sbin/grub2-probe: info: changing current directory to cpu.
/usr/sbin/grub2-probe: info: changing current directory to 0.
/usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?).

# /usr/sbin/grub2-probe -v --target=device /sysroot

/usr/sbin/grub2-probe: info: adding `hd0' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: adding `hd1' -> `/dev/vda' from device.map.
/dev/vda3
Comment 17 Radek Vykydal 2015-07-16 10:29:49 UTC 
Created attachment 1052635 [details]
2) reproducer with rhel installer

# /usr/sbin/grub2-probe -v --target=device /
(run in physical target chroot - /mnt/sysimage)

/usr/sbin/grub2-probe: info: adding `hd0' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: adding `hd1' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: changing current directory to /dev.
/usr/sbin/grub2-probe: info: changing current directory to rah_office88.
/usr/sbin/grub2-probe: info: changing current directory to virtio-ports.
/usr/sbin/grub2-probe: info: changing current directory to snd.
/usr/sbin/grub2-probe: info: changing current directory to vfio.
/usr/sbin/grub2-probe: info: changing current directory to mqueue.
/usr/sbin/grub2-probe: info: changing current directory to hugepages.
/usr/sbin/grub2-probe: info: changing current directory to bsg.
/usr/sbin/grub2-probe: info: changing current directory to disk.
/usr/sbin/grub2-probe: info: changing current directory to by-label.
/usr/sbin/grub2-probe: info: changing current directory to by-uuid.
/usr/sbin/grub2-probe: info: changing current directory to by-id.
/usr/sbin/grub2-probe: info: changing current directory to block.
/usr/sbin/grub2-probe: info: changing current directory to char.
/usr/sbin/grub2-probe: info: changing current directory to net.
/usr/sbin/grub2-probe: info: changing current directory to mapper.
/dev/mapper/rah_office88-root
Comment 18 Radek Vykydal 2015-07-16 10:34:11 UTC 
Created attachment 1052637 [details]
2) reproducer with rhel installer

Pleas disregard comment #17

# /usr/sbin/grub2-probe -v --target=device /
(run in physical target chroot - /mnt/sysimage)

/usr/sbin/grub2-probe: info: adding `hd0' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: adding `hd1' -> `/dev/vda' from device.map.
/dev/vda3
Comment 19 Radek Vykydal 2015-07-16 10:35:49 UTC 
Created attachment 1052638 [details]
3) default lvm configuration with atomic installer

# /usr/sbin/grub2-probe -v --target=device /
(run in deployment chroot)

/usr/sbin/grub2-probe: info: adding `hd0' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: adding `hd1' -> `/dev/vda' from device.map.
/usr/sbin/grub2-probe: info: changing current directory to /dev.
/usr/sbin/grub2-probe: info: changing current directory to rah_office88.
/usr/sbin/grub2-probe: info: changing current directory to virtio-ports.
/usr/sbin/grub2-probe: info: changing current directory to snd.
/usr/sbin/grub2-probe: info: changing current directory to vfio.
/usr/sbin/grub2-probe: info: changing current directory to mqueue.
/usr/sbin/grub2-probe: info: changing current directory to hugepages.
/usr/sbin/grub2-probe: info: changing current directory to bsg.
/usr/sbin/grub2-probe: info: changing current directory to disk.
/usr/sbin/grub2-probe: info: changing current directory to by-label.
/usr/sbin/grub2-probe: info: changing current directory to by-uuid.
/usr/sbin/grub2-probe: info: changing current directory to by-id.
/usr/sbin/grub2-probe: info: changing current directory to block.
/usr/sbin/grub2-probe: info: changing current directory to char.
/usr/sbin/grub2-probe: info: changing current directory to net.
/usr/sbin/grub2-probe: info: changing current directory to mapper.
/dev/mapper/rah_office88-root
Comment 20 Colin Walters 2015-10-01 18:50:46 UTC 

*** This bug has been marked as a duplicate of bug 1267860 ***
Note You need to log in before you can comment on or make changes to this bug.