Whilst running my playbook from the CLI, the run script task (check_point.mgmt.cp_mgmt_run_script) operation times out after 300 seconds and Ansible reports the task as failed.
The task continues to run in he background until completion.
Do you know which 300 second default timeout setting is causing this and where it can be modified?
Whilst running my playbook from the CLI, the run script task (check_point.mgmt.cp_mgmt_run_script) operation times out
after 300 seconds and Ansible reports the task as failed.
The task continues to run in he background until completion.
Do you know which 300 second default timeout setting is causing this and where it can be modified?
Hello Simon,
as far as I can tell there is no Ansible timeout for a task, so you need to look elsewhere for this timeout.
Which exact task in that collection is affected by the timeout?
There are 2 other timeouts, first affects connections and it relates to establishing one and/or reading from one.
The other is the ansible_command_timeout variable, which only works for specific networking modules and it is not ‘task wide’ but per command issued within the task.
I’ve tried adding the following variable directly to the playbook but it’ still timing out after 300 seconds.
The task is running a bash shell script which is copying a file from one folder location to another locally, then sequentially connecting to two remote servers via SSH and copying the file to a file share on each of those servers.
Despite Ansible reporting the task as failed, the file copy process continues to run to completion in the background.
I need to rectify the 300 second task timeout as I intend to create schedules for these scripts in AWX so require a successful job run outcome.
Playbook and debug output of ansible-playbook below.