>> The win_package action failed to execute in the expected time frame (5) >> and was terminated.
> The only time this error ever appears is if you have a timeout set on the > task [1]. Check to ensure you don't have that config entry set > 'ansible-config dump --only-changed' or haven't set it on the task play. > > [1] > https://docs.ansible.com/ansible/latest/reference_appendices/config.html#task-timeout No it's not that sadly. It times out before 5 seconds anyway. Checking ansible-config dump --only-changed it says: ANSIBLE_NOCOWS(/home/opc/vb-ansible-core/ansible.cfg) = True CALLBACKS_ENABLED(/home/opc/vb-ansible-core/ansible.cfg) = ['ansible.posix.profile_tasks'] CONFIG_FILE() = /home/opc/vb-ansible-core/ansible.cfg DEFAULT_BECOME(/home/opc/vb-ansible-core/ansible.cfg) = False DEFAULT_FORKS(/home/opc/vb-ansible-core/ansible.cfg) = 100 DEFAULT_HOST_LIST(/home/opc/vb-ansible-core/ansible.cfg) = ['/home/opc/vb-ansible-core/inventories/auto_inventory.oci.yml', '/home/opc/vb-ansible-core/invent> DEFAULT_LOG_PATH(/home/opc/vb-ansible-core/ansible.cfg) = /home/opc/vb-ansible-core/.logs/ansible.log DEFAULT_ROLES_PATH(/home/opc/vb-ansible-core/ansible.cfg) = ['/home/opc/vb-ansible-core/roles_external', '/home/opc/vb-ansible-core/roles'] DEFAULT_TIMEOUT(/home/opc/vb-ansible-core/ansible.cfg) = 30 HOST_KEY_CHECKING(/home/opc/vb-ansible-core/ansible.cfg) = False INTERPRETER_PYTHON(/home/opc/vb-ansible-core/ansible.cfg) = auto_silent RETRY_FILES_ENABLED(/home/opc/vb-ansible-core/ansible.cfg) = True RETRY_FILES_SAVE_PATH(/home/opc/vb-ansible-core/ansible.cfg) = /home/opc/.ansible-retry Moreover explicitly setting task_timeout = 60 or 0 in ansible.cfg, results in the same error. -- 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/87edej9f3i.fsf%40swift.santanas.co.za.
