Fix DM_MULTIPATH_DEVICE_PATH check in mdadm.rules (#1628192)

This value can be explicitly set to 0 (meaning 'not a multipath
device'). The check as currently written will match on this, as
it just matches absolutely any one or more characters at all,
including 0. Fix the check to only look for '1', the value that
indicates the device is multipath. This is the same as how
68-del-part-nodes.rules and 69-dm-lvm-metad.rules do it.

Resolves: bz1628192

Signed-off-by: Adam Williamson <awilliam@redhat.com>

mdadm.rules

@@ -7,7 +7,7 @@
 ENV{ANACONDA}=="?*", GOTO="md_end"
 
 # Also don't process disks that are slated to be a multipath device
-ENV{DM_MULTIPATH_DEVICE_PATH}=="?*", GOTO="md_end"
+ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="md_end"
 
 # We process add events on block devices (since they are ready as soon as
 # they are added to the system), but we must process change events as well

mdadm.spec

@@ -1,7 +1,7 @@
 Name:        mdadm
 Version:     4.1
 %define subversion rc2
-Release:     rc2.0.1%{?dist}
+Release:     rc2.0.2%{?dist}
 Summary:     The mdadm program controls Linux md devices (software RAID arrays)
 URL:         http://www.kernel.org/pub/linux/utils/raid/mdadm/
 License:     GPLv2+
@@ -92,6 +92,10 @@ install -m644 %{SOURCE8} %{buildroot}/etc/libreport/events.d
 /etc/libreport/events.d/*
 
 %changelog
+* Thu Sep 13 2018 Adam Williamson <awilliam@redhat.com> - 4.1-rc2.0.2
+- Fix multipath check in udev rule, broke array init in F29
+- Resolves bz1628192
+
 * Sun Aug 26 2018 Peter Robinson <pbrobinson@fedoraproject.org> 4.1-rc2.0.1
 - Update to 4.1 rc2