Bug 1019502

+++ This bug was initially created as a clone of Bug #955202 +++

Description of problem:
Installation to an image file fails at the end of the installation with following traceback:

Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1544, in install
    raise BootLoaderError("bootloader install failed")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1558, in write
    self.install()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2249, in writeBootLoader
    storage.bootloader.write()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall
    writeBootLoader(storage, payload, instClass, ksdata)
  File "/usr/lib64/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run
    threading.Thread.run(self, *args, **kwargs)
BootLoaderError: bootloader install failed


From storage.log:
...
10:21:28,989 INFO program: Running... grub2-install --no-floppy /dev/mapper/file
10:21:30,106 INFO program: device-mapper: table ioctl on  failed: No such device or address
10:21:30,107 INFO program: device-mapper: table ioctl on  failed: No such device or address
... (repeats 46 times)
10:21:30,120 INFO program: device-mapper: table ioctl on  failed: No such device or address
10:21:30,120 INFO program: device-mapper: table ioctl on  failed: No such device or address
10:21:30,121 INFO program: /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/mapper/file.  Check your device.map.
10:21:30,121 DEBUG program: Return code: 1

Version-Release number of selected component (if applicable):
anaconda-19.20-2.el7

How reproducible:
always

Steps to Reproduce:
1. yum install anaconda
2. dd if=/dev/zero of=/root/file.img bs=1 count=1 seek=10G
3. anaconda --graphical --image=/root/file.img --repo=<REPO_PATH>
4. proceed through the installation, select "Standard Partition" scheme, let anaconda to create partitioning
  
Actual results:
traceback at the end of the installation

Expected results:
successful installation

Additional info:

--- Additional comment from David Lehman on 2013-09-26 11:48:09 EDT ---

I have a fix for this bug, but it only revealed another problem down the line. Dracut resolves device specifications from /etc/fstab at image creation time and creates systemd unit files to wait for the existence of device files used for /, /boot, and swap. The problem is that the disk name at installation time is different from the disk name in the actual system, and the names of the systemd unit files are based on these names. In your reproducer, the image file was named "file". You would end up with a systemd unit file named "devexists-dev-mapper-file1", which would wait until the device node "/dev/mapper/file1" exists. This, of course, will never happen since the disk image is now seen as an actual disk and therefore the /boot partition is more like "/dev/vda1" or "/dev/sda1".