Comment 1 for bug 1665584

I have used strace to find out what is the reason of 'udevadm settle' timeouts. It turns out that it is a known udev issue described here [1] and kernel developers are fine with it. On the other hand, even if they will solve this issue, the patch they will write will be non-backportable for us, so there is no way to fix this issue directly. I think that the best WA will be calling 'udevadm settle' with reasonable timeout, say 15 seconds, that will allow us to fix the original bug with mpath devices being not ready at agent's startup, but will also allow us to use current agent's timeouts without flaps.

[1] https://lists.gt.net/linux/kernel/1524376