Adding a dependency requirement in multipathd.service fixes this issue. This is similar to what is done with uuidd.service.
uuidd.service (as an example) has
Required=uuidd.socket
Which enforces a (hard) dependency requirement that systemd works with. Required= makes it so that if the socket does not start, the service will also not start[0].
I would suggest adding a weaker dependency[1] using Want= in the service file. This satisfies fixing the issue in this bug and has a lower chance of causing other issues.
Adding a dependency requirement in multipathd.service fixes this issue. This is similar to what is done with uuidd.service.
uuidd.service (as an example) has uuidd.socket
Required=
Which enforces a (hard) dependency requirement that systemd works with. Required= makes it so that if the socket does not start, the service will also not start[0].
I would suggest adding a weaker dependency[1] using Want= in the service file. This satisfies fixing the issue in this bug and has a lower chance of causing other issues.
[0] - https:/ /www.freedeskto p.org/software/ systemd/ man/systemd. unit.html# Requires=
[1] - https:/ /www.freedeskto p.org/software/ systemd/ man/systemd. unit.html# Wants=