On Sun, Apr 10, 2016 at 10:43 AM, Barak Korren <bkorren(a)redhat.com&gt; wrote: > Hi there, I use the following Python SDK snippet to create a template > from an existing VM: > > templ = ovirt.templates.add( > ovirtsdk.xml.Template(vm=vm, name=vm.name) > ) > > This seems to launch a template creation task in a non-blocking > manner, which makes the next command I run, which tries to delete the > VM, fail because the VM is still locked by the template creation task. > > Is there a way to block on the template creation task and not return > to the code until it finishes? I don't think so, but you can loop waiting, see e.g.: http://www.ovirt.org/develop/api/pythonapi/#create-a-template-from-vm

-- Didi _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Sun, Apr 10, 2016 at 11:02 AM, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: > On Sun, Apr 10, 2016 at 10:43 AM, Barak Korren <bkorren(a)redhat.com&gt; > wrote: >> Hi there, I use the following Python SDK snippet to create a > template >> from an existing VM: >> >>      templ = ovirt.templates.add( >>          ovirtsdk.xml.Template(vm=vm, name=vm.name [1]) >>      ) >> >> This seems to launch a template creation task in a non-blocking >> manner, which makes the next command I run, which tries to delete > the >> VM, fail because the VM is still locked by the template creation > task. >> >> Is there a way to block on the template creation task and not > return >> to the code until it finishes? > > I don't think so, but you can loop waiting, see e.g.: > > http://www.ovirt.org/develop/api/pythonapi/#create-a-template-from-vm > [2] I wish we could have an extra parameters on the Python SDK that would do this exact loop for us, since essentially most use cases require this. I'm not sure it is relevant only for template creation, btw. What is also more annoying, is that this loop (IIRC) will never break, if something bad happens and the template ends up in a state != down (such as locked). (Same issue I've just had with host installation - Iv'e waited endlessly for it to be in 'up' state, only to find out it ended in 'installed_failed' state). Y.

> -- > Didi > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users [3] Links: ------ [1] http://vm.name [2] http://www.ovirt.org/develop/api/pythonapi/#create-a-template-from-vm [3] http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Sun, Apr 10, 2016 at 11:02 AM, Yedidyah Bar David <didi(a)redhat.com <mailto:didi@redhat.com>> wrote: On Sun, Apr 10, 2016 at 10:43 AM, Barak Korren <bkorren(a)redhat.com <mailto:bkorren@redhat.com>> wrote: > Hi there, I use the following Python SDK snippet to create a template > from an existing VM: > > templ = ovirt.templates.add( > ovirtsdk.xml.Template(vm=vm, name=vm.name <http://vm.name>) > ) > > This seems to launch a template creation task in a non-blocking > manner, which makes the next command I run, which tries to delete the > VM, fail because the VM is still locked by the template creation task. > > Is there a way to block on the template creation task and not return > to the code until it finishes? I don't think so, but you can loop waiting, see e.g.: http://www.ovirt.org/develop/api/pythonapi/#create-a-template-from-vm I wish we could have an extra parameters on the Python SDK that would do this exact loop for us, since essentially most use cases require this. I'm not sure it is relevant only for template creation, btw. What is also more annoying, is that this loop (IIRC) will never break, if something bad happens and the template ends up in a state != down (such as locked). (Same issue I've just had with host installation - Iv'e waited endlessly for it to be in 'up' state, only to find out it ended in 'installed_failed' state). Y.