I just created the following test with a faked lsblk command, because this is called in https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/facts/hardware/linux.py#L400
* created a /usr/local/bin/lsblk bash script with "sleep 10" * check that my faked lsblk command is used: which lsblk: /usr/local/bin/lsblk * set in ansible.cfg "gather_timeout = 1" * run "time ansible testhost -b -m setup", this took 12 seconds, no warning shown * run "time ansible-playbook facts.yaml -b -l testhost" (facts.yaml is a playbook which just gather facts), his took 12 seconds, no warning shown I'm sure that my faked lsblk command is used, because when I change the sleep from 10 to 20, the ansible and ansible-playbook runs take 22 instead of the previous 12 seconds. I would expect a warning from the above ansible and ansible-playbook runs, but nothing is shown. Brian Coca schrieb am Dienstag, 11. Mai 2021 um 16:54:43 UTC+2: > 2.3.3 didn't do timeouts correctly, that might be the reason you are > seeing this now, but you should also get a warning about it. > > > -- > ---------- > Brian Coca > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b82bf9ef-a1ec-45b1-b2d8-1c4cd44a8d53n%40googlegroups.com.
