given that
find /usr/lib/dracut/modules.d -type f \ -iname 11-dm.rules \ -o -iname 59-persistent-storage-dm.rules \ -o -iname 59-persistent-storage-md.rules \ -o -iname 59-persistent-storage.rules \ -o -iname 61-persistent-storage.rules \ -o -iname 64-lvm.rules \ -o -iname 65-md-incremental-imsm.rules /usr/lib/dracut/modules.d/90dm/11-dm.rules /usr/lib/dracut/modules.d/90dm/59-persistent-storage-dm.rules /usr/lib/dracut/modules.d/90mdraid/59-persistent-storage-md.rules /usr/lib/dracut/modules.d/90mdraid/65-md-incremental-imsm.rules /usr/lib/dracut/modules.d/95udev-rules/59-persistent-storage.rules /usr/lib/dracut/modules.d/95udev-rules/61-persistent-storage.rules /usr/lib/dracut/modules.d/90lvm/64-lvm.rules
and a comment @ #fedora-devel "that sounds like a dracut bug" i'm still a bit fuzzy on following the udev rules path logic thru systemd-udevd, dracut and udev itself, but this https://github.com/dracutdevs/dracut/blob/master/dracut-init.sh#L515 , or its neighborhood, looks involved, if not also suspect.
