<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Sep 23, 2015 at 8:26 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Sep 23, 2015 at 8:21 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Wed, Sep 23, 2015 at 12:40 PM, Ian Fraser <span dir="ltr"><<a href="mailto:Ian.Fraser@asm.org.uk" target="_blank">Ian.Fraser@asm.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Nir,<br>
<br>
I have changed the v2v.py file as per your request, it has now changed the behaviour. The popup window still hangs and I get the following two events:<br>
<br>
Failed to retrieve VMs information from external server vpx://username%40domain@vcenter.server/datacentre_name/hostname?no_verify=1<br>
<br>
VDSM ovirt-host-02 command failed: internal error: Invalid or not yet handled value 'emptyBackingString' for VMX entry 'ide1:0.fileName' for device type 'cdrom-image'<br></blockquote><div><br></div></span><div>Fixing the first error, we see now the real error; libvirt cannot handle this vm configuration. We will ask one of the libvirt guys to look into this.</div></div></div></div></blockquote></span></div></div></div></blockquote><div><br></div><div>In vdsm.log, we see that one vm was parsed successfully (it failed when geting disk info):</div><div><br></div><div><div>Thread-1076::ERROR::2015-09-23 10:18:51,778::v2v::682::root::(_add_disk_info) Error getting disk size</div><div>Traceback (most recent call last):</div><div> File "/usr/share/vdsm/v2v.py", line 679, in _add_disk_info</div><div> vol = conn.storageVolLookupByPath(disk['alias'])</div><div> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4308, in storageVolLookupByPath</div><div> if ret is None:raise libvirtError('virStorageVolLookupByPath() failed', conn=self)</div><div>libvirtError: An error occurred, but the cause is unknown</div><div><br></div><div>Little later, libvirt failed to return the xml for another vm:<br></div><div><br></div><div>Thread-1076::ERROR::2015-09-23 10:18:52,604::__init__::526::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error</div><div>Traceback (most recent call last):</div><div> File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 521, in _serveRequest</div><div> res = method(**params)</div><div> File "/usr/share/vdsm/rpc/Bridge.py", line 273, in _dynamicMethod</div><div> result = fn(*methodArgs)</div><div> File "/usr/share/vdsm/API.py", line 1436, in getExternalVMs</div><div> return v2v.get_external_vms(uri, username, password)</div><div> File "/usr/share/vdsm/v2v.py", line 152, in get_external_vms</div><div> root = ET.fromstring(vm.XMLDesc(0))</div><div> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 478, in XMLDesc</div><div> if ret is None: raise libvirtError ('virDomainGetXMLDesc() failed', dom=self)</div><div>libvirtError: internal error: Invalid or not yet handled value 'emptyBackingString' for VMX entry 'ide1:0.fileName' for device type 'cdrom-image'</div></div><div><br></div><div>It is possible that the failing vm was the one you want to import, but it is also possible that the vm you want to import was fine.</div><div><br></div><div>The following patch improve error handling, so we are not aborting the entire request if libvirt fail to return the domain xml for one of the vms.</div><div><a href="https://gerrit.ovirt.org/46634/">https://gerrit.ovirt.org/46634/</a><br></div><div><br></div><div><div>Please test the patch and report if it works for you.</div></div><div><br></div><div>Nir</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>You may try to disable the cdrom device on that vm, which is probably useless now.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I have attached the vdsm.log to this email, should I also attach to the BZ I opened?</blockquote><div><br></div></span><div>Yes, please attach it.</div></div></div></div></blockquote><div><br></div></span><div>Hmm, this is a new issue, as the original issue is solved by the patch.</div><div><br></div><div>Please open a new bug for the libvirt error:</div><span class=""><div><br></div><div>internal error: Invalid or not yet handled value 'emptyBackingString' for VMX entry 'ide1:0.fileName' for device type 'cdrom-image'<br></div><div><br></div></span><div>Thanks,</div><div>Nir</div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>(Adding back <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>, since this thread may help others with same issue.)</div><div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Many thanks<br>
<br>
Ian<br>
<span><br>
From: Nir Soffer [mailto:<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>]<br>
</span>Sent: 23 September 2015 00:04<br>
To: Ian Fraser <<a href="mailto:Ian.Fraser@asm.org.uk" target="_blank">Ian.Fraser@asm.org.uk</a>>; Shahar Havivi <<a href="mailto:shavivi@redhat.com" target="_blank">shavivi@redhat.com</a>><br>
<div><div>Cc: <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><br>
Subject: Re: [ovirt-users] vmware import hangs after click load button on 3.5 rc5<br>
<br>
Hi Ian,<br>
<br>
Your import failed because looking up some disk failed. Unfortunately, we don't have enough information in the log abut this failure.<br>
<br>
Because of incorrect error handling, this error failed the entire request, failing your import.<br>
<br>
Patch [1] fixes the second problem. If is possible that with this patch listing the external vms will work and you will be able to import the vm, but it is also possible that the first error was significant and will fail the import later.<br>
<br>
It would be useful if you test this patch and report if it works for you.<br>
<br>
Would you open an ovirt bug for this issue, attaching the vdsm log?<br>
<br>
[1] <a href="https://gerrit.ovirt.org/46540" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/46540</a><br>
<br>
Nir<br>
<br>
On Tue, Sep 22, 2015 at 9:09 AM, Ian Fraser <<a href="mailto:Ian.Fraser@asm.org.uk" target="_blank">Ian.Fraser@asm.org.uk</a>> wrote:<br>
Thanks Nir,<br>
<br>
File attached.<br>
<br>
From: Nir Soffer [mailto:<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>]<br>
Sent: 21 September 2015 23:16<br>
To: Ian Fraser <<a href="mailto:Ian.Fraser@asm.org.uk" target="_blank">Ian.Fraser@asm.org.uk</a>><br>
Cc: <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><br>
Subject: Re: [ovirt-users] vmware import hangs after click load button on 3.5 rc5<br>
<br>
On Tue, Sep 22, 2015 at 12:14 AM, Ian Fraser <<a href="mailto:Ian.Fraser@asm.org.uk" target="_blank">Ian.Fraser@asm.org.uk</a>> wrote:<br>
I did get a “VDSM <hostname> command failed: local variable 'capacity' referenced before assignment” error in the events I have just noticed, does that shed any more light?<br>
<br>
This shed some light. Can you share the vdsm.log containing this error?<br>
<br>
Look in /var/log/vdsm/vdsm.log*<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit <a href="http://www.symanteccloud.com" rel="noreferrer" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
<br>
</div></div>________________________________________<br>
<div><div><br>
The information in this message and any attachment is intended for the addressee and is confidential. If you are not that addressee, no action should be taken in reliance on the information and you should please reply to this message immediately to inform us of incorrect receipt and destroy this message and any attachments.<br>
<br>
For the purposes of internet level email security incoming and outgoing emails may be read by personnel other than the named recipient or sender.<br>
<br>
Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee that emails and attachments are virus free or compatible with your systems. You should make your own checks and ASM (UK) Ltd does not accept liability in respect of viruses or computer problems experienced.<br>
Registered address: Agency Sector Management (UK) Ltd. Ashford House, 41-45 Church Road, Ashford, Middlesex, TW15 2TQ<br>
Registered in England No.2053849<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit <a href="http://www.symanteccloud.com" rel="noreferrer" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit <a href="http://www.symanteccloud.com" rel="noreferrer" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
<br>
________________________________<br>
<br>
The information in this message and any attachment is intended for the addressee and is confidential. If you are not that addressee, no action should be taken in reliance on the information and you should please reply to this message immediately to inform us of incorrect receipt and destroy this message and any attachments.<br>
<br>
For the purposes of internet level email security incoming and outgoing emails may be read by personnel other than the named recipient or sender.<br>
<br>
Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee that emails and attachments are virus free or compatible with your systems. You should make your own checks and ASM (UK) Ltd does not accept liability in respect of viruses or computer problems experienced.<br>
Registered address: Agency Sector Management (UK) Ltd. Ashford House, 41-45 Church Road, Ashford, Middlesex, TW15 2TQ<br>
Registered in England No.2053849<br>
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
For more information please visit <a href="http://www.symanteccloud.com" rel="noreferrer" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div>