On Fri, Jul 19, 2019 at 4:14 PM Gianluca Cecchi <gianluca.cec...@gmail.com> wrote:
> On Fri, Jul 19, 2019 at 3:15 PM Gianluca Cecchi <gianluca.cec...@gmail.com> > wrote: > >> >> >> In engine.log the first error I see is 30 minutes after start >> >> 2019-07-19 12:25:31,563+02 ERROR >> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] >> (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] Ansible >> playbook execution failed: Timeout occurred while executing Ansible >> playbook. >> > > In the mean time, as the playbook seems this one ( I run the job from > engine) : /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml > > Based on what described in bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1697301 I created at the moment the file /etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf with ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80 and restarted the engine and the python script to verify Just to see if it completes, even if in my case with a 30Gb preallocated disk, the source problem is qemu-img convert command very slow in I/O. It reads from iscsi multipath (2 paths) with 2x3MB/s and it writes on nfs If I run a dd command from iscsi device mapper device to an nfs file I have 140MB/s rate that is what expected based on my storage array performances and my network. Not understood why the qemu-img command is so slow The question still applies in case I have to do an appliance from a VM with a very big disk, where the copy could potentially have an elapsed of more that 30 minutes... Gianluca
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DMUARHYE34JLJRAX3BLEPV54EK2CS5SD/
