Hello, in the past when I was in 4.3.7 I used this file: /etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf with ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80 to bypass the default of 30 minutes at that time. I updated in steps to 4.3.8 (in February), 4.3.9 (in April) and 4.3.10 (in July). Due to an error on my side I noticed that the task for which I extended the ansible timeout (this task I didn't execute anymore in latest months) fails with timeout after 80 minutes indeed. With the intent to extend again the custom timeout I went to /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf, provided by ovirt-engine-backend-4.3.10.4-1.el7.noarch and actually I see this inside: " # Specify the ansible-playbook command execution timeout in minutes. It's used for any task, which executes # AnsibleExecutor class. To change the value permanentaly create a conf file 99-ansible-playbook-timeout.conf in # /etc/ovirt-engine/engine.conf.d/ ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=120 " and the file seems the original provided, not tampered: [root@ovmgr1 test_backup]# rpm -qvV ovirt-engine-backend-4.3.10.4-1.el7.noarch | grep virt-engine.conf$ ......... /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf [root@ovmgr1 test_backup]# So the question is: has the default intended value passed to 120 in 4.3.10 (or in any version after 4.3.7)? Thanks, Gianluca _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WXFVIYC4LYO...