On Fri, Aug 09, 2019 at 02:58:18AM +0300, Nir Soffer wrote:
On Thu, Aug 8, 2019 at 5:05 PM Richard W.M. Jones
<rjones(a)redhat.com> wrote:
> > + if disk.status == types.DiskStatus.OK:
> > + debug("finalized after %s seconds", time.time()
-
> start)
>
Maybe this was the real error? (using , instead of %)
I fixed this in a later build. However the error we're talking about
here seems to be unrelated to it.
...
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> line 37334, in remove
> self._internal_remove(headers, query, wait)
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 271, in _internal_remove
> return future.wait() if wait else future
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 55, in wait
> return self._code(response)
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 268, in callback
> self._check_fault(response)
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 132, in _check_fault
> self._raise_error(response, body)
> ', ' File
"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 118, in _raise_error
> raise error
> ', 'Error: Fault reason is "Operation Failed". Fault detail is
"[Cannot
> remove Virtual Disk. Related operation is currently in progress. Please try
> again later.]". HTTP response code is 409.
> ']
>
I think this error means that the disk is currently busy, probably because
of the real error.
Ilanit, can you share complete virt-v2v and daemon logs?
These are quite large so I uploaded them here:
http://oirase.annexia.org/tmp/v2v-import-20190808T125134-439694.log
http://oirase.annexia.org/tmp/v2v-import-20190808T125134-439694-wrapper.log
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html