Hi,
The more testing i do, the more it appears like issue may be with ansible
2.10.8 (with python 3.9.2) or maybe the fact that iam using ansible on WSL
(windows subsystem for linux) debian linux.
I have implemented an workaround in which i have modified
ansible_comamnd_timeout in ansible.cfg
Hi Dick,
I assumed script and playbook were synonymous with each other. I ran
playbook using the command ansible-playbook sample.yaml. Again, i didn't
mention it because i assumed this is the only way to run (unless ad hoc
command is used), so i didn't think it was important enough to mention.
Not an actual answer but some hints for the future
On Tue, 31 Aug 2021 at 20:10, Vikram S wrote:
> Hi,
>
> Iam using Ansible 2.10 with python 3 in WSL linux. In ansible.cfg file, i
> set global timeout value as 180.
>
> i also set much higher ansible_command_timeout value for certain tasks.
> Ho
Hi,
Iam using Ansible 2.10 with python 3 in WSL linux. In ansible.cfg file, i
set global timeout value as 180.
i also set much higher ansible_command_timeout value for certain tasks.
However these tasks end in error as ansible shows that command timeout of
180 secs happened. So for some reason
