Currently booty tries to create device.map entries for / even when
there is a separate /boot. There is no reason to have device.map
entries when there is a separate /boot, and booty trips over when
trying to do this for complicated layered setups.
Removing the creating of device.map entries for devices backing /
worksaround this falling over. Note the second patch in this set
actually fixes the specific case of falling over happening in bug
593718, and both are intended for rhel6-branch to make booty more
robust wrt this.
Related: rhbz#593718
---
booty/x86.py | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/booty/x86.py b/booty/x86.py
index 89d6393..01ac93d 100644
--- a/booty/x86.py
+++ b/booty/x86.py
@@ -221,7 +221,6 @@ class x86BootloaderInfo(efiBootloaderInfo):
# keep track of which devices are used for the device.map
usedDevs = set()
usedDevs.update(self.getPhysicalDevices(grubTarget))
- usedDevs.update(self.getPhysicalDevices(rootDev.name))
usedDevs.update(self.getPhysicalDevices(bootDev.name))
usedDevs.update([dev for (label, longlabel, dev) in chainList if longlabel])
--
1.7.0.1
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
