There is an issue with 'udevadm settle' command described at [1]. It
turns out that inconsistent task IDs stored in queue.bin and
uevent_seqnum could cause udevadm settle to loop trying to find
the task that doesn't exist. Kernel developers are skeptical about
this issue and not willing to fix it, but even if they will, we
still will take it to MOS.
By default, it uses a timeout of 180 seconds that is inconsistent
with a set of existing nailgun-agent's timeouts. We can remove this
check, absence of it shouldn't break anything.
Reviewed: https:/ /review. fuel-infra. org/38899
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka
Commit: dd5fc8ed168ab77 14e8ca1bfb6cc15 2c448f6704
Author: Oleksiy Molchanov <email address hidden>
Date: Tue Jul 17 12:34:38 2018
Udevadm settle loops
There is an issue with 'udevadm settle' command described at [1]. It
turns out that inconsistent task IDs stored in queue.bin and
uevent_seqnum could cause udevadm settle to loop trying to find
the task that doesn't exist. Kernel developers are skeptical about
this issue and not willing to fix it, but even if they will, we
still will take it to MOS.
By default, it uses a timeout of 180 seconds that is inconsistent
with a set of existing nailgun-agent's timeouts. We can remove this
check, absence of it shouldn't break anything.
[1] https:/ /lists. gt.net/ linux/kernel/ 1524376
Change-Id: I0e71786c351646 3496a313ea17438 582a45ad2aa
Closes-bug: #1665584