This is probably a hack and not an ideal solution, however it is the
lesser of two evils AFAICT. Multipath SAN devices pop up as iSCSI
devices in syslog and even bear some iSCSI-related udev info, as well
as some FCoE-related udev info; however, not enough to match as either
an iSCSI or FCoE device and trigger installation of the relevant
dracut-network package.
Didn't want to go messing with the udev functions since those look quite
fragile, so this seemed a safer option, since the devices are getting
detected as multipath devices at least.
Resolves: rhbz#1007463
---
storage/devices.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/storage/devices.py b/storage/devices.py
index 1c99ac8..c55915c 100644
--- a/storage/devices.py
+++ b/storage/devices.py
@@ -3333,7 +3333,7 @@ class DMRaidArrayDevice(DMDevice):
class MultipathDevice(DMDevice):
""" A multipath device """
_type = "dm-multipath"
- _packages = ["device-mapper-multipath"]
+ _packages = ["device-mapper-multipath", "dracut-network"]
_services = ["multipathd"]
_partitionable = True
_isDisk = True
--
1.8.3.1