Its looks like key SSHInactivityHardTimeoutSeconds was the source of my grief.
On 3/15/2020 at 10:14 AM, "Jayme" wrote:This is all that should be needed, I've done so on my engine and it works fine to set the timeout much higher. My guess is that you did not restart the engine after changing the config. On Sun, Mar 15, 2020 at 10:44 AM Barrett Richardson wrote: Version 4.2.8.2-1.0.9.el7 Per the info near the bottom of /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf I should be able to create this file, /etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf and place in the file these contents, ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=150 and extend the playbook timeout. It doesn't work, still times out after 30 minutes. Any suggested workarounds? _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/UMKQAVQQIN6XU6LL4ZZDEBZH5DWZDMH6/
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/SNWCIYZ6BXALC6WTCTHLZVFU5CNVWKNQ/
