From: David Lehman <dlehman(a)redhat.com>
multipath itself has absolutely no identifying metadata, so whatever
metadata found on the member is related to the multipath set's
formatting -- not the the multipath set itself (as is normally the case
when metadata is associated with a member of a container/aggregate
device). The same metadata should appear in the udev entry for the
multipath, so we can (and should) ignore it in the members' entries.
Resolves: rhbz#1254232
---
blivet/populator.py | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/blivet/populator.py b/blivet/populator.py
index 7aaf3e1..dc97b08 100644
--- a/blivet/populator.py
+++ b/blivet/populator.py
@@ -1449,6 +1449,12 @@ def handleUdevDeviceFormat(self, info, device):
# overarching volume UUID will be stored as volUUID
kwargs["uuid"] = info["ID_FS_UUID_SUB"]
kwargs["volUUID"] = uuid
+ elif format_type == "multipath_member":
+ # blkid does not care that the UUID it sees on a multipath member is
+ # for the multipath set's (and not the member's) formatting, so we
+ # have to discard it.
+ kwargs.pop("uuid")
+ kwargs.pop("label")
try:
log.info("type detected on '%s' is '%s'", name,
format_designator)
--
To view this commit on github, visit
https://github.com/rhinstaller/blivet/commit/d478f1fb4d68a3a342bed28b43ff...