udev: propagate errors in udev_event_execute_rules()
And do not set initialized flag to the device.
This means that because /dev/dm-0 does not get created in this situation, udev gives up before running the RUN command that was accumulated during rule processing.
The upstream change seems to make sense really but the failure mode is pretty unfortunate. I think for the purpose of getting livecd-rootfs builds going again we could/should switch to a wrapper around mount -o loop,offset=xxx and avoid all this devicemapper complexity...
Ah hah, it's this upstream commit: https:/ /github. com/systemd/ systemd/ commit/ 99058cd66ad3070 7d8eda32d6b256e 5c05bbf46a
commit 99058cd66ad3070 7d8eda32d6b256e 5c05bbf46a
Author: Yu Watanabe <email address hidden>
Date: Wed Jun 5 03:09:20 2019 +0900
udev: propagate errors in udev_event_ execute_ rules()
And do not set initialized flag to the device.
This means that because /dev/dm-0 does not get created in this situation, udev gives up before running the RUN command that was accumulated during rule processing.
The upstream change seems to make sense really but the failure mode is pretty unfortunate. I think for the purpose of getting livecd-rootfs builds going again we could/should switch to a wrapper around mount -o loop,offset=xxx and avoid all this devicemapper complexity...