<div dir="ltr">Bug ID 1358828. I can do another for the direct import of the OVF (without virt-v2v) if needed.<br><div><br></div><div>Cheers,</div><div><br></div><div>Cam</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi <span dir="ltr"><<a href="mailto:shavivi@redhat.com" target="_blank">shavivi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 21.07.16 14:38, Cam Mac wrote:<br>
> I tried that already, and it fails. I gave it another try with the GUI on<br>
> the new VM I created, as you described, and it fails.<br>
> I can attach the engine log if you like.<br>
</span>no need,<br>
please file a bug and attach the ova (without the disks - its a tar file that<br>
you can edit)<br>
<div class="HOEnZb"><div class="h5">><br>
> Thanks,<br>
><br>
> Cam<br>
><br>
> On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi <<a href="mailto:shavivi@redhat.com">shavivi@redhat.com</a>> wrote:<br>
><br>
> > On 21.07.16 14:01, Campbell McLeay wrote:<br>
> > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes<br>
> > > of testing the import again with a new hostname, and it failed with<br>
> > > the same error.<br>
> > What you are trying to do is as far as I understand is to use virt-v2v<br>
> > utility<br>
> > to put the ova in export domain, there may be something wrong between the<br>
> > virt-v2v output ovf and the oVirt engine.<br>
> > You can try the new feature to import ova strait on oVirt admin portal (if<br>
> > you<br>
> > already try that the forget it), go to the vms tab -> import and select<br>
> > "vmware ova" from the select box...<br>
> ><br>
> > ><br>
> > > Cheers,<br>
> > ><br>
> > > Cam<br>
> > ><br>
> > > On 21 July 2016 at 12:59, Shahar Havivi <<a href="mailto:shavivi@redhat.com">shavivi@redhat.com</a>> wrote:<br>
> > > > On 21.07.16 14:58, Shahar Havivi wrote:<br>
> > > >> The error looks like you have a problem in the storage pool which is<br>
> > null by<br>
> > > >> the log.<br>
> > > >><br>
> > > >> Please open a bug and specify the exact steps that you took,<br>
> > > >> ie.<br>
> > > >> 1. $ virt-v2v -o rhev ...<br>
> > > >> 2. goto the admin portal and try to view the VMs in the export domain<br>
> > > >> 3. etc...<br>
> > > >><br>
> > > >> If you can attach the ova without the disk it will be great.<br>
> > > > And please attach the engine.log as well.<br>
> > > >><br>
> > > >> Shahar.<br>
> > > >><br>
> > > >> On 21.07.16 10:16, Cam Mac wrote:<br>
> > > >> > Sent, thanks Shahar.<br>
> > > >> ><br>
> > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <<a href="mailto:shavivi@redhat.com">shavivi@redhat.com</a>><br>
> > wrote:<br>
> > > >> ><br>
> > > >> > > On 21.07.16 10:03, Cam Mac wrote:<br>
> > > >> > > OK,<br>
> > > >> > > Can you please share the engine.log<br>
> > > >> > > > Hi Shahar,<br>
> > > >> > > ><br>
> > > >> > > > Doesn't appear to be there:<br>
> > > >> > > ><br>
> > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';<br>
> > > >> > > > vm_name<br>
> > > >> > > > ---------<br>
> > > >> > > > (0 rows)<br>
> > > >> > > ><br>
> > > >> > > > Thanks,<br>
> > > >> > > ><br>
> > > >> > > > Cam<br>
> > > >> > > ><br>
> > > >> > > ><br>
> > > >> > > ><br>
> > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <<br>
> > <a href="mailto:shavivi@redhat.com">shavivi@redhat.com</a>><br>
> > > >> > > wrote:<br>
> > > >> > > ><br>
> > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:<br>
> > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:<br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > > The import doesn't happen automatically, you have to do<br>
> > the final<br>
> > > >> > > > > step<br>
> > > >> > > > > > > > manually (when using the command line). See:<br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > > <a href="http://libguestfs.org/virt-v2v.1.html#output-to-rhev" rel="noreferrer" target="_blank">http://libguestfs.org/virt-v2v.1.html#output-to-rhev</a><br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > > However that error shouldn't happen. It looks like the<br>
> > name is<br>
> > > >> > > the<br>
> > > >> > > > > > > > same as the name of an existing VM. From virt-v2v you<br>
> > can do the<br>
> > > >> > > > > > > > whole conversion/import over again, this time adding<br>
> > the `-on<br>
> > > >> > > > > > > > new_name' option to the command line (obviously<br>
> > choosing a name<br>
> > > >> > > which<br>
> > > >> > > > > > > > is not otherwise being used).<br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > > I don't know if there's a way to get oVirt to change<br>
> > the name<br>
> > > >> > > when<br>
> > > >> > > > > > > > importing from the export domain. As far as I know you<br>
> > have to<br>
> > > >> > > start<br>
> > > >> > > > > > > > the import from scratch.<br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > ><br>
> > > >> > > > > > > There's no existing VM with that name that I can see. It<br>
> > may have<br>
> > > >> > > come<br>
> > > >> > > > > from<br>
> > > >> > > > > > > one of my earlier import attempts,<br>
> > > >> > > > > > > though that earlier attempt did not show up in the GUI,<br>
> > it did<br>
> > > >> > > write<br>
> > > >> > > > > files<br>
> > > >> > > > > > > to the export domain.<br>
> > > >> > > > > > ><br>
> > > >> > > > > > > I re-ran the conversion again with a rename but it failed<br>
> > to<br>
> > > >> > > import it<br>
> > > >> > > > > > > again, with the same error.<br>
> > > >> > > > > > ><br>
> > > >> > > > > > > Could there be a record in the DB somewhere, or does it<br>
> > look at the<br>
> > > >> > > > > files<br>
> > > >> > > > > > > alone? Just trying to work out where the conflict is.<br>
> > > >> > > > > ><br>
> > > >> > > > > > I had a look at the ovirt-engine code where<br>
> > > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it<br>
> > appears to come<br>
> > > >> > > > > > from a database check. However I'm not really familiar<br>
> > enough with<br>
> > > >> > > > > > the code to be sure. Probably best to ask an oVirt<br>
> > developer, or try<br>
> > > >> > > > > > dumping the database to see if "wvm2" appears in a column<br>
> > anywhere.<br>
> > > >> > > > > ><br>
> > > >> > > > > > Rich.<br>
> > > >> > > > > ><br>
> > > >> > > > > > --<br>
> > > >> > > > > > Richard Jones, Virtualization Group, Red Hat<br>
> > > >> > > > > <a href="http://people.redhat.com/~rjones" rel="noreferrer" target="_blank">http://people.redhat.com/~rjones</a><br>
> > > >> > > > > > Read my programming and virtualization blog:<br>
> > > >> > > <a href="http://rwmj.wordpress.com" rel="noreferrer" target="_blank">http://rwmj.wordpress.com</a><br>
> > > >> > > > > > Fedora Windows cross-compiler. Compile Windows programs,<br>
> > test, and<br>
> > > >> > > > > > build Windows installers. Over 100 libraries supported.<br>
> > > >> > > > > > <a href="http://fedoraproject.org/wiki/MinGW" rel="noreferrer" target="_blank">http://fedoraproject.org/wiki/MinGW</a><br>
> > > >> > > > > It may be in the DB...<br>
> > > >> > > > > Try to run this via psql:<br>
> > > >> > > > ><br>
> > > >> > > > > select vm_name from vm_static where vm_name='wvm2';<br>
> > > >> > > > ><br>
> > > >> > > > > and see if there is a result...<br>
> > > >> > > > ><br>
> > > >> > ><br>
> > > > _______________________________________________<br>
> > > > Users mailing list<br>
> > > > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > > > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<br>
> > > Campbell McLeay · Senior Systems Administrator<br>
> > ><br>
> > > London · New York · Los Angeles · Montréal<br>
> > > T <a href="tel:%2B44%20%280%2920%207344%208000" value="+442073448000">+44 (0)20 7344 8000</a><br>
> > > 19-23 Wells Street, London W1T 3PQ<br>
> > > Twitter · Facebook · <a href="http://framestore.com" rel="noreferrer" target="_blank">framestore.com</a><br>
> ><br>
</div></div></blockquote></div><br></div>