Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 16:24, Cam Mac wrote:
> Bug ID 1358828. I can do another for the direct import of the OVF (without
Thanks,
Please attach the ovf and ova (no need for the disk inside the ova) to the
bug.
> virt-v2v) if needed.
> 
> Cheers,
> 
> Cam
> 
> On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi  wrote:
> 
> > On 21.07.16 14:38, Cam Mac wrote:
> > > I tried that already, and it fails. I gave it another try with the GUI on
> > > the new VM I created, as you described, and it fails.
> > > I can attach the engine log if you like.
> > no need,
> > please file a bug and attach the ova (without the disks - its a tar file
> > that
> > you can edit)
> > >
> > > Thanks,
> > >
> > > Cam
> > >
> > > On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi 
> > wrote:
> > >
> > > > On 21.07.16 14:01, Campbell McLeay wrote:
> > > > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > > > > of testing the import again with a new hostname, and it failed with
> > > > > the same error.
> > > > What you are trying to do is as far as I understand is to use virt-v2v
> > > > utility
> > > > to put the ova in export domain, there may be something wrong between
> > the
> > > > virt-v2v output ovf and the oVirt engine.
> > > > You can try the new feature to import ova strait on oVirt admin portal
> > (if
> > > > you
> > > > already try that the forget it), go to the vms tab -> import and select
> > > > "vmware ova" from the select box...
> > > >
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Cam
> > > > >
> > > > > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > > > > On 21.07.16 14:58, Shahar Havivi wrote:
> > > > > >> The error looks like you have a problem in the storage pool which
> > is
> > > > null by
> > > > > >> the log.
> > > > > >>
> > > > > >> Please open a bug and specify the exact steps that you took,
> > > > > >> ie.
> > > > > >> 1. $ virt-v2v -o rhev ...
> > > > > >> 2. goto the admin portal and try to view the VMs in the export
> > domain
> > > > > >> 3. etc...
> > > > > >>
> > > > > >> If you can attach the ova without the disk it will be great.
> > > > > > And please attach the engine.log as well.
> > > > > >>
> > > > > >> Shahar.
> > > > > >>
> > > > > >> On 21.07.16 10:16, Cam Mac wrote:
> > > > > >> > Sent, thanks Shahar.
> > > > > >> >
> > > > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <
> > shav...@redhat.com>
> > > > wrote:
> > > > > >> >
> > > > > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > > > > >> > > OK,
> > > > > >> > > Can you please share the engine.log
> > > > > >> > > > Hi Shahar,
> > > > > >> > > >
> > > > > >> > > > Doesn't appear to be there:
> > > > > >> > > >
> > > > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > > > >> > > >  vm_name
> > > > > >> > > > -
> > > > > >> > > > (0 rows)
> > > > > >> > > >
> > > > > >> > > > Thanks,
> > > > > >> > > >
> > > > > >> > > > Cam
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> > > > shav...@redhat.com>
> > > > > >> > > wrote:
> > > > > >> > > >
> > > > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > >> > > > > > > >
> > > > > >> > > > > > > > The import doesn't happen automatically, you have
> > to do
> > > > the final
> > > > > >> > > > > step
> > > > > >> > > > > > > > manually (when using the command line).  See:
> > > > > >> > > > > > > >
> > > > > >> > > > > > > >
> > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > >> > > > > > > >
> > > > > >> > > > > > > > However that error shouldn't happen.  It looks like
> > the
> > > > name is
> > > > > >> > > the
> > > > > >> > > > > > > > same as the name of an existing VM.  From virt-v2v
> > you
> > > > can do the
> > > > > >> > > > > > > > whole conversion/import over again, this time adding
> > > > the `-on
> > > > > >> > > > > > > > new_name' option to the command line (obviously
> > > > choosing a name
> > > > > >> > > which
> > > > > >> > > > > > > > is not otherwise being used).
> > > > > >> > > > > > > >
> > > > > >> > > > > > > > I don't know if there's a way to get oVirt to change
> > > > the name
> > > > > >> > > when
> > > > > >> > > > > > > > importing from the export domain.  As far as I know
> > you
> > > > have to
> > > > > >> > > start
> > > > > >> > > > > > > > the import from scratch.
> > > > > >> > > > > > > >
> > > > > >> > > > > > > >
> > > > > >> > > > > > > There's no existing VM with that name that I can see.
> > It
> > > > may have
> > > > > >> > > come
> > > > > >> > > > > from
> > > > > >> > > > > > > one of my earlier import attempts,
> > > > > >> > > > > > > though that earlier attempt did not show up in the
> > GUI,
> > > > it did
> > > > > >> > > write
> > > > > >> > > > > files
> > > > > >> > > > > > > to the export domain.
> > > > > >> > > > > > >
> > > 

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Bug ID 1358828. I can do another for the direct import of the OVF (without
virt-v2v) if needed.

Cheers,

Cam

On Thu, Jul 21, 2016 at 2:56 PM, Shahar Havivi  wrote:

> On 21.07.16 14:38, Cam Mac wrote:
> > I tried that already, and it fails. I gave it another try with the GUI on
> > the new VM I created, as you described, and it fails.
> > I can attach the engine log if you like.
> no need,
> please file a bug and attach the ova (without the disks - its a tar file
> that
> you can edit)
> >
> > Thanks,
> >
> > Cam
> >
> > On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi 
> wrote:
> >
> > > On 21.07.16 14:01, Campbell McLeay wrote:
> > > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > > > of testing the import again with a new hostname, and it failed with
> > > > the same error.
> > > What you are trying to do is as far as I understand is to use virt-v2v
> > > utility
> > > to put the ova in export domain, there may be something wrong between
> the
> > > virt-v2v output ovf and the oVirt engine.
> > > You can try the new feature to import ova strait on oVirt admin portal
> (if
> > > you
> > > already try that the forget it), go to the vms tab -> import and select
> > > "vmware ova" from the select box...
> > >
> > > >
> > > > Cheers,
> > > >
> > > > Cam
> > > >
> > > > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > > > On 21.07.16 14:58, Shahar Havivi wrote:
> > > > >> The error looks like you have a problem in the storage pool which
> is
> > > null by
> > > > >> the log.
> > > > >>
> > > > >> Please open a bug and specify the exact steps that you took,
> > > > >> ie.
> > > > >> 1. $ virt-v2v -o rhev ...
> > > > >> 2. goto the admin portal and try to view the VMs in the export
> domain
> > > > >> 3. etc...
> > > > >>
> > > > >> If you can attach the ova without the disk it will be great.
> > > > > And please attach the engine.log as well.
> > > > >>
> > > > >> Shahar.
> > > > >>
> > > > >> On 21.07.16 10:16, Cam Mac wrote:
> > > > >> > Sent, thanks Shahar.
> > > > >> >
> > > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi <
> shav...@redhat.com>
> > > wrote:
> > > > >> >
> > > > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > > > >> > > OK,
> > > > >> > > Can you please share the engine.log
> > > > >> > > > Hi Shahar,
> > > > >> > > >
> > > > >> > > > Doesn't appear to be there:
> > > > >> > > >
> > > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > > >> > > >  vm_name
> > > > >> > > > -
> > > > >> > > > (0 rows)
> > > > >> > > >
> > > > >> > > > Thanks,
> > > > >> > > >
> > > > >> > > > Cam
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> > > shav...@redhat.com>
> > > > >> > > wrote:
> > > > >> > > >
> > > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > >> > > > > > > >
> > > > >> > > > > > > > The import doesn't happen automatically, you have
> to do
> > > the final
> > > > >> > > > > step
> > > > >> > > > > > > > manually (when using the command line).  See:
> > > > >> > > > > > > >
> > > > >> > > > > > > >
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > >> > > > > > > >
> > > > >> > > > > > > > However that error shouldn't happen.  It looks like
> the
> > > name is
> > > > >> > > the
> > > > >> > > > > > > > same as the name of an existing VM.  From virt-v2v
> you
> > > can do the
> > > > >> > > > > > > > whole conversion/import over again, this time adding
> > > the `-on
> > > > >> > > > > > > > new_name' option to the command line (obviously
> > > choosing a name
> > > > >> > > which
> > > > >> > > > > > > > is not otherwise being used).
> > > > >> > > > > > > >
> > > > >> > > > > > > > I don't know if there's a way to get oVirt to change
> > > the name
> > > > >> > > when
> > > > >> > > > > > > > importing from the export domain.  As far as I know
> you
> > > have to
> > > > >> > > start
> > > > >> > > > > > > > the import from scratch.
> > > > >> > > > > > > >
> > > > >> > > > > > > >
> > > > >> > > > > > > There's no existing VM with that name that I can see.
> It
> > > may have
> > > > >> > > come
> > > > >> > > > > from
> > > > >> > > > > > > one of my earlier import attempts,
> > > > >> > > > > > > though that earlier attempt did not show up in the
> GUI,
> > > it did
> > > > >> > > write
> > > > >> > > > > files
> > > > >> > > > > > > to the export domain.
> > > > >> > > > > > >
> > > > >> > > > > > > I re-ran the conversion again with a rename but it
> failed
> > > to
> > > > >> > > import it
> > > > >> > > > > > > again, with the same error.
> > > > >> > > > > > >
> > > > >> > > > > > > Could there be a record in the DB somewhere, or does
> it
> > > look at the
> > > > >> > > > > files
> > > > >> > > > > > > alone? Just trying to work out where the conflict is.
> > > > >> > > > > >

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:38, Cam Mac wrote:
> I tried that already, and it fails. I gave it another try with the GUI on
> the new VM I created, as you described, and it fails.
> I can attach the engine log if you like.
no need,
please file a bug and attach the ova (without the disks - its a tar file that
you can edit)
> 
> Thanks,
> 
> Cam
> 
> On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi  wrote:
> 
> > On 21.07.16 14:01, Campbell McLeay wrote:
> > > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > > of testing the import again with a new hostname, and it failed with
> > > the same error.
> > What you are trying to do is as far as I understand is to use virt-v2v
> > utility
> > to put the ova in export domain, there may be something wrong between the
> > virt-v2v output ovf and the oVirt engine.
> > You can try the new feature to import ova strait on oVirt admin portal (if
> > you
> > already try that the forget it), go to the vms tab -> import and select
> > "vmware ova" from the select box...
> >
> > >
> > > Cheers,
> > >
> > > Cam
> > >
> > > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > > On 21.07.16 14:58, Shahar Havivi wrote:
> > > >> The error looks like you have a problem in the storage pool which is
> > null by
> > > >> the log.
> > > >>
> > > >> Please open a bug and specify the exact steps that you took,
> > > >> ie.
> > > >> 1. $ virt-v2v -o rhev ...
> > > >> 2. goto the admin portal and try to view the VMs in the export domain
> > > >> 3. etc...
> > > >>
> > > >> If you can attach the ova without the disk it will be great.
> > > > And please attach the engine.log as well.
> > > >>
> > > >> Shahar.
> > > >>
> > > >> On 21.07.16 10:16, Cam Mac wrote:
> > > >> > Sent, thanks Shahar.
> > > >> >
> > > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi 
> > wrote:
> > > >> >
> > > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > > >> > > OK,
> > > >> > > Can you please share the engine.log
> > > >> > > > Hi Shahar,
> > > >> > > >
> > > >> > > > Doesn't appear to be there:
> > > >> > > >
> > > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > >> > > >  vm_name
> > > >> > > > -
> > > >> > > > (0 rows)
> > > >> > > >
> > > >> > > > Thanks,
> > > >> > > >
> > > >> > > > Cam
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> > shav...@redhat.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > >> > > > > > > >
> > > >> > > > > > > > The import doesn't happen automatically, you have to do
> > the final
> > > >> > > > > step
> > > >> > > > > > > > manually (when using the command line).  See:
> > > >> > > > > > > >
> > > >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > >> > > > > > > >
> > > >> > > > > > > > However that error shouldn't happen.  It looks like the
> > name is
> > > >> > > the
> > > >> > > > > > > > same as the name of an existing VM.  From virt-v2v you
> > can do the
> > > >> > > > > > > > whole conversion/import over again, this time adding
> > the `-on
> > > >> > > > > > > > new_name' option to the command line (obviously
> > choosing a name
> > > >> > > which
> > > >> > > > > > > > is not otherwise being used).
> > > >> > > > > > > >
> > > >> > > > > > > > I don't know if there's a way to get oVirt to change
> > the name
> > > >> > > when
> > > >> > > > > > > > importing from the export domain.  As far as I know you
> > have to
> > > >> > > start
> > > >> > > > > > > > the import from scratch.
> > > >> > > > > > > >
> > > >> > > > > > > >
> > > >> > > > > > > There's no existing VM with that name that I can see. It
> > may have
> > > >> > > come
> > > >> > > > > from
> > > >> > > > > > > one of my earlier import attempts,
> > > >> > > > > > > though that earlier attempt did not show up in the GUI,
> > it did
> > > >> > > write
> > > >> > > > > files
> > > >> > > > > > > to the export domain.
> > > >> > > > > > >
> > > >> > > > > > > I re-ran the conversion again with a rename but it failed
> > to
> > > >> > > import it
> > > >> > > > > > > again, with the same error.
> > > >> > > > > > >
> > > >> > > > > > > Could there be a record in the DB somewhere, or does it
> > look at the
> > > >> > > > > files
> > > >> > > > > > > alone? Just trying to work out where the conflict is.
> > > >> > > > > >
> > > >> > > > > > I had a look at the ovirt-engine code where
> > > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it
> > appears to come
> > > >> > > > > > from a database check.  However I'm not really familiar
> > enough with
> > > >> > > > > > the code to be sure.  Probably best to ask an oVirt
> > developer, or try
> > > >> > > > > > dumping the database to see if "wvm2" appears in a column
> > anywhere.
> > > >> > > > > >
> > > >> > > > > > 

Re: [ovirt-users] Import of ova failed

[Cam Mac]

I tried that already, and it fails. I gave it another try with the GUI on
the new VM I created, as you described, and it fails.
I can attach the engine log if you like.

Thanks,

Cam

On Thu, Jul 21, 2016 at 2:17 PM, Shahar Havivi  wrote:

> On 21.07.16 14:01, Campbell McLeay wrote:
> > Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> > of testing the import again with a new hostname, and it failed with
> > the same error.
> What you are trying to do is as far as I understand is to use virt-v2v
> utility
> to put the ova in export domain, there may be something wrong between the
> virt-v2v output ovf and the oVirt engine.
> You can try the new feature to import ova strait on oVirt admin portal (if
> you
> already try that the forget it), go to the vms tab -> import and select
> "vmware ova" from the select box...
>
> >
> > Cheers,
> >
> > Cam
> >
> > On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > > On 21.07.16 14:58, Shahar Havivi wrote:
> > >> The error looks like you have a problem in the storage pool which is
> null by
> > >> the log.
> > >>
> > >> Please open a bug and specify the exact steps that you took,
> > >> ie.
> > >> 1. $ virt-v2v -o rhev ...
> > >> 2. goto the admin portal and try to view the VMs in the export domain
> > >> 3. etc...
> > >>
> > >> If you can attach the ova without the disk it will be great.
> > > And please attach the engine.log as well.
> > >>
> > >> Shahar.
> > >>
> > >> On 21.07.16 10:16, Cam Mac wrote:
> > >> > Sent, thanks Shahar.
> > >> >
> > >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi 
> wrote:
> > >> >
> > >> > > On 21.07.16 10:03, Cam Mac wrote:
> > >> > > OK,
> > >> > > Can you please share the engine.log
> > >> > > > Hi Shahar,
> > >> > > >
> > >> > > > Doesn't appear to be there:
> > >> > > >
> > >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > >> > > >  vm_name
> > >> > > > -
> > >> > > > (0 rows)
> > >> > > >
> > >> > > > Thanks,
> > >> > > >
> > >> > > > Cam
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi <
> shav...@redhat.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > >> > > > > > > >
> > >> > > > > > > > The import doesn't happen automatically, you have to do
> the final
> > >> > > > > step
> > >> > > > > > > > manually (when using the command line).  See:
> > >> > > > > > > >
> > >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > >> > > > > > > >
> > >> > > > > > > > However that error shouldn't happen.  It looks like the
> name is
> > >> > > the
> > >> > > > > > > > same as the name of an existing VM.  From virt-v2v you
> can do the
> > >> > > > > > > > whole conversion/import over again, this time adding
> the `-on
> > >> > > > > > > > new_name' option to the command line (obviously
> choosing a name
> > >> > > which
> > >> > > > > > > > is not otherwise being used).
> > >> > > > > > > >
> > >> > > > > > > > I don't know if there's a way to get oVirt to change
> the name
> > >> > > when
> > >> > > > > > > > importing from the export domain.  As far as I know you
> have to
> > >> > > start
> > >> > > > > > > > the import from scratch.
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > There's no existing VM with that name that I can see. It
> may have
> > >> > > come
> > >> > > > > from
> > >> > > > > > > one of my earlier import attempts,
> > >> > > > > > > though that earlier attempt did not show up in the GUI,
> it did
> > >> > > write
> > >> > > > > files
> > >> > > > > > > to the export domain.
> > >> > > > > > >
> > >> > > > > > > I re-ran the conversion again with a rename but it failed
> to
> > >> > > import it
> > >> > > > > > > again, with the same error.
> > >> > > > > > >
> > >> > > > > > > Could there be a record in the DB somewhere, or does it
> look at the
> > >> > > > > files
> > >> > > > > > > alone? Just trying to work out where the conflict is.
> > >> > > > > >
> > >> > > > > > I had a look at the ovirt-engine code where
> > >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it
> appears to come
> > >> > > > > > from a database check.  However I'm not really familiar
> enough with
> > >> > > > > > the code to be sure.  Probably best to ask an oVirt
> developer, or try
> > >> > > > > > dumping the database to see if "wvm2" appears in a column
> anywhere.
> > >> > > > > >
> > >> > > > > > Rich.
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Richard Jones, Virtualization Group, Red Hat
> > >> > > > > http://people.redhat.com/~rjones
> > >> > > > > > Read my programming and virtualization blog:
> > >> > > http://rwmj.wordpress.com
> > >> > > > > > Fedora Windows cross-compiler. Compile Windows programs,
> test, and
> > >> > > > > > build Windows installers. Over 100 libraries supported.

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:01, Campbell McLeay wrote:
> Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
> of testing the import again with a new hostname, and it failed with
> the same error.
What you are trying to do is as far as I understand is to use virt-v2v utility
to put the ova in export domain, there may be something wrong between the
virt-v2v output ovf and the oVirt engine.
You can try the new feature to import ova strait on oVirt admin portal (if you
already try that the forget it), go to the vms tab -> import and select
"vmware ova" from the select box...

> 
> Cheers,
> 
> Cam
> 
> On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> > On 21.07.16 14:58, Shahar Havivi wrote:
> >> The error looks like you have a problem in the storage pool which is null 
> >> by
> >> the log.
> >>
> >> Please open a bug and specify the exact steps that you took,
> >> ie.
> >> 1. $ virt-v2v -o rhev ...
> >> 2. goto the admin portal and try to view the VMs in the export domain
> >> 3. etc...
> >>
> >> If you can attach the ova without the disk it will be great.
> > And please attach the engine.log as well.
> >>
> >> Shahar.
> >>
> >> On 21.07.16 10:16, Cam Mac wrote:
> >> > Sent, thanks Shahar.
> >> >
> >> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  
> >> > wrote:
> >> >
> >> > > On 21.07.16 10:03, Cam Mac wrote:
> >> > > OK,
> >> > > Can you please share the engine.log
> >> > > > Hi Shahar,
> >> > > >
> >> > > > Doesn't appear to be there:
> >> > > >
> >> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> >> > > >  vm_name
> >> > > > -
> >> > > > (0 rows)
> >> > > >
> >> > > > Thanks,
> >> > > >
> >> > > > Cam
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> >> > > wrote:
> >> > > >
> >> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> >> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> >> > > > > > > >
> >> > > > > > > > The import doesn't happen automatically, you have to do the 
> >> > > > > > > > final
> >> > > > > step
> >> > > > > > > > manually (when using the command line).  See:
> >> > > > > > > >
> >> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> >> > > > > > > >
> >> > > > > > > > However that error shouldn't happen.  It looks like the name 
> >> > > > > > > > is
> >> > > the
> >> > > > > > > > same as the name of an existing VM.  From virt-v2v you can 
> >> > > > > > > > do the
> >> > > > > > > > whole conversion/import over again, this time adding the `-on
> >> > > > > > > > new_name' option to the command line (obviously choosing a 
> >> > > > > > > > name
> >> > > which
> >> > > > > > > > is not otherwise being used).
> >> > > > > > > >
> >> > > > > > > > I don't know if there's a way to get oVirt to change the name
> >> > > when
> >> > > > > > > > importing from the export domain.  As far as I know you have 
> >> > > > > > > > to
> >> > > start
> >> > > > > > > > the import from scratch.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > There's no existing VM with that name that I can see. It may 
> >> > > > > > > have
> >> > > come
> >> > > > > from
> >> > > > > > > one of my earlier import attempts,
> >> > > > > > > though that earlier attempt did not show up in the GUI, it did
> >> > > write
> >> > > > > files
> >> > > > > > > to the export domain.
> >> > > > > > >
> >> > > > > > > I re-ran the conversion again with a rename but it failed to
> >> > > import it
> >> > > > > > > again, with the same error.
> >> > > > > > >
> >> > > > > > > Could there be a record in the DB somewhere, or does it look 
> >> > > > > > > at the
> >> > > > > files
> >> > > > > > > alone? Just trying to work out where the conflict is.
> >> > > > > >
> >> > > > > > I had a look at the ovirt-engine code where
> >> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
> >> > > > > > come
> >> > > > > > from a database check.  However I'm not really familiar enough 
> >> > > > > > with
> >> > > > > > the code to be sure.  Probably best to ask an oVirt developer, 
> >> > > > > > or try
> >> > > > > > dumping the database to see if "wvm2" appears in a column 
> >> > > > > > anywhere.
> >> > > > > >
> >> > > > > > Rich.
> >> > > > > >
> >> > > > > > --
> >> > > > > > Richard Jones, Virtualization Group, Red Hat
> >> > > > > http://people.redhat.com/~rjones
> >> > > > > > Read my programming and virtualization blog:
> >> > > http://rwmj.wordpress.com
> >> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, 
> >> > > > > > and
> >> > > > > > build Windows installers. Over 100 libraries supported.
> >> > > > > > http://fedoraproject.org/wiki/MinGW
> >> > > > > It may be in the DB...
> >> > > > > Try to run this via psql:
> >> > > > >
> >> > > > > select vm_name from vm_static where vm_name='wvm2';
> >> > > > >
> >> > > > > and see if there is a result...
> >> > > > >
> >> > >
> > 

Re: [ovirt-users] Import of ova failed

[Campbell McLeay]

Thanks Shahar. Will do. I created a new VM on VMWare for the purposes
of testing the import again with a new hostname, and it failed with
the same error.

Cheers,

Cam

On 21 July 2016 at 12:59, Shahar Havivi  wrote:
> On 21.07.16 14:58, Shahar Havivi wrote:
>> The error looks like you have a problem in the storage pool which is null by
>> the log.
>>
>> Please open a bug and specify the exact steps that you took,
>> ie.
>> 1. $ virt-v2v -o rhev ...
>> 2. goto the admin portal and try to view the VMs in the export domain
>> 3. etc...
>>
>> If you can attach the ova without the disk it will be great.
> And please attach the engine.log as well.
>>
>> Shahar.
>>
>> On 21.07.16 10:16, Cam Mac wrote:
>> > Sent, thanks Shahar.
>> >
>> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
>> >
>> > > On 21.07.16 10:03, Cam Mac wrote:
>> > > OK,
>> > > Can you please share the engine.log
>> > > > Hi Shahar,
>> > > >
>> > > > Doesn't appear to be there:
>> > > >
>> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
>> > > >  vm_name
>> > > > -
>> > > > (0 rows)
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Cam
>> > > >
>> > > >
>> > > >
>> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
>> > > wrote:
>> > > >
>> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
>> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
>> > > > > > > >
>> > > > > > > > The import doesn't happen automatically, you have to do the 
>> > > > > > > > final
>> > > > > step
>> > > > > > > > manually (when using the command line).  See:
>> > > > > > > >
>> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>> > > > > > > >
>> > > > > > > > However that error shouldn't happen.  It looks like the name is
>> > > the
>> > > > > > > > same as the name of an existing VM.  From virt-v2v you can do 
>> > > > > > > > the
>> > > > > > > > whole conversion/import over again, this time adding the `-on
>> > > > > > > > new_name' option to the command line (obviously choosing a name
>> > > which
>> > > > > > > > is not otherwise being used).
>> > > > > > > >
>> > > > > > > > I don't know if there's a way to get oVirt to change the name
>> > > when
>> > > > > > > > importing from the export domain.  As far as I know you have to
>> > > start
>> > > > > > > > the import from scratch.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > There's no existing VM with that name that I can see. It may have
>> > > come
>> > > > > from
>> > > > > > > one of my earlier import attempts,
>> > > > > > > though that earlier attempt did not show up in the GUI, it did
>> > > write
>> > > > > files
>> > > > > > > to the export domain.
>> > > > > > >
>> > > > > > > I re-ran the conversion again with a rename but it failed to
>> > > import it
>> > > > > > > again, with the same error.
>> > > > > > >
>> > > > > > > Could there be a record in the DB somewhere, or does it look at 
>> > > > > > > the
>> > > > > files
>> > > > > > > alone? Just trying to work out where the conflict is.
>> > > > > >
>> > > > > > I had a look at the ovirt-engine code where
>> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
>> > > > > > come
>> > > > > > from a database check.  However I'm not really familiar enough with
>> > > > > > the code to be sure.  Probably best to ask an oVirt developer, or 
>> > > > > > try
>> > > > > > dumping the database to see if "wvm2" appears in a column anywhere.
>> > > > > >
>> > > > > > Rich.
>> > > > > >
>> > > > > > --
>> > > > > > Richard Jones, Virtualization Group, Red Hat
>> > > > > http://people.redhat.com/~rjones
>> > > > > > Read my programming and virtualization blog:
>> > > http://rwmj.wordpress.com
>> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
>> > > > > > build Windows installers. Over 100 libraries supported.
>> > > > > > http://fedoraproject.org/wiki/MinGW
>> > > > > It may be in the DB...
>> > > > > Try to run this via psql:
>> > > > >
>> > > > > select vm_name from vm_static where vm_name='wvm2';
>> > > > >
>> > > > > and see if there is a result...
>> > > > >
>> > >
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users



-- 
Campbell McLeay · Senior Systems Administrator

London · New York · Los Angeles · Montréal
T  +44 (0)20 7344 8000
19-23 Wells Street, London W1T 3PQ
Twitter · Facebook · framestore.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 14:58, Shahar Havivi wrote:
> The error looks like you have a problem in the storage pool which is null by
> the log.
> 
> Please open a bug and specify the exact steps that you took,
> ie.
> 1. $ virt-v2v -o rhev ...
> 2. goto the admin portal and try to view the VMs in the export domain
> 3. etc...
> 
> If you can attach the ova without the disk it will be great.
And please attach the engine.log as well.
> 
> Shahar.
> 
> On 21.07.16 10:16, Cam Mac wrote:
> > Sent, thanks Shahar.
> > 
> > On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
> > 
> > > On 21.07.16 10:03, Cam Mac wrote:
> > > OK,
> > > Can you please share the engine.log
> > > > Hi Shahar,
> > > >
> > > > Doesn't appear to be there:
> > > >
> > > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > > >  vm_name
> > > > -
> > > > (0 rows)
> > > >
> > > > Thanks,
> > > >
> > > > Cam
> > > >
> > > >
> > > >
> > > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> > > wrote:
> > > >
> > > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > > > >
> > > > > > > > The import doesn't happen automatically, you have to do the 
> > > > > > > > final
> > > > > step
> > > > > > > > manually (when using the command line).  See:
> > > > > > > >
> > > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > > > >
> > > > > > > > However that error shouldn't happen.  It looks like the name is
> > > the
> > > > > > > > same as the name of an existing VM.  From virt-v2v you can do 
> > > > > > > > the
> > > > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > > > new_name' option to the command line (obviously choosing a name
> > > which
> > > > > > > > is not otherwise being used).
> > > > > > > >
> > > > > > > > I don't know if there's a way to get oVirt to change the name
> > > when
> > > > > > > > importing from the export domain.  As far as I know you have to
> > > start
> > > > > > > > the import from scratch.
> > > > > > > >
> > > > > > > >
> > > > > > > There's no existing VM with that name that I can see. It may have
> > > come
> > > > > from
> > > > > > > one of my earlier import attempts,
> > > > > > > though that earlier attempt did not show up in the GUI, it did
> > > write
> > > > > files
> > > > > > > to the export domain.
> > > > > > >
> > > > > > > I re-ran the conversion again with a rename but it failed to
> > > import it
> > > > > > > again, with the same error.
> > > > > > >
> > > > > > > Could there be a record in the DB somewhere, or does it look at 
> > > > > > > the
> > > > > files
> > > > > > > alone? Just trying to work out where the conflict is.
> > > > > >
> > > > > > I had a look at the ovirt-engine code where
> > > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to 
> > > > > > come
> > > > > > from a database check.  However I'm not really familiar enough with
> > > > > > the code to be sure.  Probably best to ask an oVirt developer, or 
> > > > > > try
> > > > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > > > >
> > > > > > Rich.
> > > > > >
> > > > > > --
> > > > > > Richard Jones, Virtualization Group, Red Hat
> > > > > http://people.redhat.com/~rjones
> > > > > > Read my programming and virtualization blog:
> > > http://rwmj.wordpress.com
> > > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > > > build Windows installers. Over 100 libraries supported.
> > > > > > http://fedoraproject.org/wiki/MinGW
> > > > > It may be in the DB...
> > > > > Try to run this via psql:
> > > > >
> > > > > select vm_name from vm_static where vm_name='wvm2';
> > > > >
> > > > > and see if there is a result...
> > > > >
> > >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

The error looks like you have a problem in the storage pool which is null by
the log.

Please open a bug and specify the exact steps that you took,
ie.
1. $ virt-v2v -o rhev ...
2. goto the admin portal and try to view the VMs in the export domain
3. etc...

If you can attach the ova without the disk it will be great.

Shahar.

On 21.07.16 10:16, Cam Mac wrote:
> Sent, thanks Shahar.
> 
> On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:
> 
> > On 21.07.16 10:03, Cam Mac wrote:
> > OK,
> > Can you please share the engine.log
> > > Hi Shahar,
> > >
> > > Doesn't appear to be there:
> > >
> > > engine=> select vm_name from vm_static where vm_name='wvm2';
> > >  vm_name
> > > -
> > > (0 rows)
> > >
> > > Thanks,
> > >
> > > Cam
> > >
> > >
> > >
> > > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> > wrote:
> > >
> > > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > > >
> > > > > > > The import doesn't happen automatically, you have to do the final
> > > > step
> > > > > > > manually (when using the command line).  See:
> > > > > > >
> > > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > > >
> > > > > > > However that error shouldn't happen.  It looks like the name is
> > the
> > > > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > > new_name' option to the command line (obviously choosing a name
> > which
> > > > > > > is not otherwise being used).
> > > > > > >
> > > > > > > I don't know if there's a way to get oVirt to change the name
> > when
> > > > > > > importing from the export domain.  As far as I know you have to
> > start
> > > > > > > the import from scratch.
> > > > > > >
> > > > > > >
> > > > > > There's no existing VM with that name that I can see. It may have
> > come
> > > > from
> > > > > > one of my earlier import attempts,
> > > > > > though that earlier attempt did not show up in the GUI, it did
> > write
> > > > files
> > > > > > to the export domain.
> > > > > >
> > > > > > I re-ran the conversion again with a rename but it failed to
> > import it
> > > > > > again, with the same error.
> > > > > >
> > > > > > Could there be a record in the DB somewhere, or does it look at the
> > > > files
> > > > > > alone? Just trying to work out where the conflict is.
> > > > >
> > > > > I had a look at the ovirt-engine code where
> > > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > > > from a database check.  However I'm not really familiar enough with
> > > > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > > >
> > > > > Rich.
> > > > >
> > > > > --
> > > > > Richard Jones, Virtualization Group, Red Hat
> > > > http://people.redhat.com/~rjones
> > > > > Read my programming and virtualization blog:
> > http://rwmj.wordpress.com
> > > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > > build Windows installers. Over 100 libraries supported.
> > > > > http://fedoraproject.org/wiki/MinGW
> > > > It may be in the DB...
> > > > Try to run this via psql:
> > > >
> > > > select vm_name from vm_static where vm_name='wvm2';
> > > >
> > > > and see if there is a result...
> > > >
> >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Sent, thanks Shahar.

On Thu, Jul 21, 2016 at 10:05 AM, Shahar Havivi  wrote:

> On 21.07.16 10:03, Cam Mac wrote:
> OK,
> Can you please share the engine.log
> > Hi Shahar,
> >
> > Doesn't appear to be there:
> >
> > engine=> select vm_name from vm_static where vm_name='wvm2';
> >  vm_name
> > -
> > (0 rows)
> >
> > Thanks,
> >
> > Cam
> >
> >
> >
> > On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi 
> wrote:
> >
> > > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > > >
> > > > > > The import doesn't happen automatically, you have to do the final
> > > step
> > > > > > manually (when using the command line).  See:
> > > > > >
> > > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > > >
> > > > > > However that error shouldn't happen.  It looks like the name is
> the
> > > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > > whole conversion/import over again, this time adding the `-on
> > > > > > new_name' option to the command line (obviously choosing a name
> which
> > > > > > is not otherwise being used).
> > > > > >
> > > > > > I don't know if there's a way to get oVirt to change the name
> when
> > > > > > importing from the export domain.  As far as I know you have to
> start
> > > > > > the import from scratch.
> > > > > >
> > > > > >
> > > > > There's no existing VM with that name that I can see. It may have
> come
> > > from
> > > > > one of my earlier import attempts,
> > > > > though that earlier attempt did not show up in the GUI, it did
> write
> > > files
> > > > > to the export domain.
> > > > >
> > > > > I re-ran the conversion again with a rename but it failed to
> import it
> > > > > again, with the same error.
> > > > >
> > > > > Could there be a record in the DB somewhere, or does it look at the
> > > files
> > > > > alone? Just trying to work out where the conflict is.
> > > >
> > > > I had a look at the ovirt-engine code where
> > > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > > from a database check.  However I'm not really familiar enough with
> > > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > > dumping the database to see if "wvm2" appears in a column anywhere.
> > > >
> > > > Rich.
> > > >
> > > > --
> > > > Richard Jones, Virtualization Group, Red Hat
> > > http://people.redhat.com/~rjones
> > > > Read my programming and virtualization blog:
> http://rwmj.wordpress.com
> > > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > > build Windows installers. Over 100 libraries supported.
> > > > http://fedoraproject.org/wiki/MinGW
> > > It may be in the DB...
> > > Try to run this via psql:
> > >
> > > select vm_name from vm_static where vm_name='wvm2';
> > >
> > > and see if there is a result...
> > >
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 21.07.16 10:03, Cam Mac wrote:
OK,
Can you please share the engine.log
> Hi Shahar,
> 
> Doesn't appear to be there:
> 
> engine=> select vm_name from vm_static where vm_name='wvm2';
>  vm_name
> -
> (0 rows)
> 
> Thanks,
> 
> Cam
> 
> 
> 
> On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi  wrote:
> 
> > On 20.07.16 20:06, Richard W.M. Jones wrote:
> > > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > > >
> > > > > The import doesn't happen automatically, you have to do the final
> > step
> > > > > manually (when using the command line).  See:
> > > > >
> > > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > > >
> > > > > However that error shouldn't happen.  It looks like the name is the
> > > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > > whole conversion/import over again, this time adding the `-on
> > > > > new_name' option to the command line (obviously choosing a name which
> > > > > is not otherwise being used).
> > > > >
> > > > > I don't know if there's a way to get oVirt to change the name when
> > > > > importing from the export domain.  As far as I know you have to start
> > > > > the import from scratch.
> > > > >
> > > > >
> > > > There's no existing VM with that name that I can see. It may have come
> > from
> > > > one of my earlier import attempts,
> > > > though that earlier attempt did not show up in the GUI, it did write
> > files
> > > > to the export domain.
> > > >
> > > > I re-ran the conversion again with a rename but it failed to import it
> > > > again, with the same error.
> > > >
> > > > Could there be a record in the DB somewhere, or does it look at the
> > files
> > > > alone? Just trying to work out where the conflict is.
> > >
> > > I had a look at the ovirt-engine code where
> > > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > > from a database check.  However I'm not really familiar enough with
> > > the code to be sure.  Probably best to ask an oVirt developer, or try
> > > dumping the database to see if "wvm2" appears in a column anywhere.
> > >
> > > Rich.
> > >
> > > --
> > > Richard Jones, Virtualization Group, Red Hat
> > http://people.redhat.com/~rjones
> > > Read my programming and virtualization blog: http://rwmj.wordpress.com
> > > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > > build Windows installers. Over 100 libraries supported.
> > > http://fedoraproject.org/wiki/MinGW
> > It may be in the DB...
> > Try to run this via psql:
> >
> > select vm_name from vm_static where vm_name='wvm2';
> >
> > and see if there is a result...
> >
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Hi Shahar,

Doesn't appear to be there:

engine=> select vm_name from vm_static where vm_name='wvm2';
 vm_name
-
(0 rows)

Thanks,

Cam



On Thu, Jul 21, 2016 at 8:33 AM, Shahar Havivi  wrote:

> On 20.07.16 20:06, Richard W.M. Jones wrote:
> > On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > > >
> > > > The import doesn't happen automatically, you have to do the final
> step
> > > > manually (when using the command line).  See:
> > > >
> > > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > > >
> > > > However that error shouldn't happen.  It looks like the name is the
> > > > same as the name of an existing VM.  From virt-v2v you can do the
> > > > whole conversion/import over again, this time adding the `-on
> > > > new_name' option to the command line (obviously choosing a name which
> > > > is not otherwise being used).
> > > >
> > > > I don't know if there's a way to get oVirt to change the name when
> > > > importing from the export domain.  As far as I know you have to start
> > > > the import from scratch.
> > > >
> > > >
> > > There's no existing VM with that name that I can see. It may have come
> from
> > > one of my earlier import attempts,
> > > though that earlier attempt did not show up in the GUI, it did write
> files
> > > to the export domain.
> > >
> > > I re-ran the conversion again with a rename but it failed to import it
> > > again, with the same error.
> > >
> > > Could there be a record in the DB somewhere, or does it look at the
> files
> > > alone? Just trying to work out where the conflict is.
> >
> > I had a look at the ovirt-engine code where
> > ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> > from a database check.  However I'm not really familiar enough with
> > the code to be sure.  Probably best to ask an oVirt developer, or try
> > dumping the database to see if "wvm2" appears in a column anywhere.
> >
> > Rich.
> >
> > --
> > Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> > Read my programming and virtualization blog: http://rwmj.wordpress.com
> > Fedora Windows cross-compiler. Compile Windows programs, test, and
> > build Windows installers. Over 100 libraries supported.
> > http://fedoraproject.org/wiki/MinGW
> It may be in the DB...
> Try to run this via psql:
>
> select vm_name from vm_static where vm_name='wvm2';
>
> and see if there is a result...
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 20.07.16 20:06, Richard W.M. Jones wrote:
> On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> > >
> > > The import doesn't happen automatically, you have to do the final step
> > > manually (when using the command line).  See:
> > >
> > > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> > >
> > > However that error shouldn't happen.  It looks like the name is the
> > > same as the name of an existing VM.  From virt-v2v you can do the
> > > whole conversion/import over again, this time adding the `-on
> > > new_name' option to the command line (obviously choosing a name which
> > > is not otherwise being used).
> > >
> > > I don't know if there's a way to get oVirt to change the name when
> > > importing from the export domain.  As far as I know you have to start
> > > the import from scratch.
> > >
> > >
> > There's no existing VM with that name that I can see. It may have come from
> > one of my earlier import attempts,
> > though that earlier attempt did not show up in the GUI, it did write files
> > to the export domain.
> > 
> > I re-ran the conversion again with a rename but it failed to import it
> > again, with the same error.
> > 
> > Could there be a record in the DB somewhere, or does it look at the files
> > alone? Just trying to work out where the conflict is.
> 
> I had a look at the ovirt-engine code where
> ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
> from a database check.  However I'm not really familiar enough with
> the code to be sure.  Probably best to ask an oVirt developer, or try
> dumping the database to see if "wvm2" appears in a column anywhere.
> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
It may be in the DB...
Try to run this via psql:

select vm_name from vm_static where vm_name='wvm2';

and see if there is a result...
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Richard W.M. Jones]

On Wed, Jul 20, 2016 at 07:16:32PM +0100, Cam Mac wrote:
> >
> > The import doesn't happen automatically, you have to do the final step
> > manually (when using the command line).  See:
> >
> > http://libguestfs.org/virt-v2v.1.html#output-to-rhev
> >
> > However that error shouldn't happen.  It looks like the name is the
> > same as the name of an existing VM.  From virt-v2v you can do the
> > whole conversion/import over again, this time adding the `-on
> > new_name' option to the command line (obviously choosing a name which
> > is not otherwise being used).
> >
> > I don't know if there's a way to get oVirt to change the name when
> > importing from the export domain.  As far as I know you have to start
> > the import from scratch.
> >
> >
> There's no existing VM with that name that I can see. It may have come from
> one of my earlier import attempts,
> though that earlier attempt did not show up in the GUI, it did write files
> to the export domain.
> 
> I re-ran the conversion again with a rename but it failed to import it
> again, with the same error.
> 
> Could there be a record in the DB somewhere, or does it look at the files
> alone? Just trying to work out where the conflict is.

I had a look at the ovirt-engine code where
ACTION_TYPE_FAILED_NAME_ALREADY_USED is raised and it appears to come
from a database check.  However I'm not really familiar enough with
the code to be sure.  Probably best to ask an oVirt developer, or try
dumping the database to see if "wvm2" appears in a column anywhere.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

>
> The import doesn't happen automatically, you have to do the final step
> manually (when using the command line).  See:
>
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>
> However that error shouldn't happen.  It looks like the name is the
> same as the name of an existing VM.  From virt-v2v you can do the
> whole conversion/import over again, this time adding the `-on
> new_name' option to the command line (obviously choosing a name which
> is not otherwise being used).
>
> I don't know if there's a way to get oVirt to change the name when
> importing from the export domain.  As far as I know you have to start
> the import from scratch.
>
>
There's no existing VM with that name that I can see. It may have come from
one of my earlier import attempts,
though that earlier attempt did not show up in the GUI, it did write files
to the export domain.

I re-ran the conversion again with a rename but it failed to import it
again, with the same error.

Could there be a record in the DB somewhere, or does it look at the files
alone? Just trying to work out where the conflict is.


Thanks,

-C


> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines.  Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Richard W.M. Jones]

On Wed, Jul 20, 2016 at 06:37:38PM +0100, Cam Mac wrote:
> It did show up in the list of importable VMs
> under the 'Import VM' tab under
> the export domain. I tried importing it from there but it gave me:
> 
> 2016-07-20 18:27:24,518 INFO
>  [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (default
> task-317) [27b3ad4b] Lock freed to object
> 'EngineLock:{exclusiveLocks='[wvm2= ACTION_TYPE_FAILED_NAME_ALREADY_USED>,
> 7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c= ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]',
> sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c= ACTION_TYPE_FAILED_VM_IS_BEING_IMPORTED$VmName wvm2>]'}'
> 
> So I guess it is doing the import still.

The import doesn't happen automatically, you have to do the final step
manually (when using the command line).  See:

http://libguestfs.org/virt-v2v.1.html#output-to-rhev

However that error shouldn't happen.  It looks like the name is the
same as the name of an existing VM.  From virt-v2v you can do the
whole conversion/import over again, this time adding the `-on
new_name' option to the command line (obviously choosing a name which
is not otherwise being used).

I don't know if there's a way to get oVirt to change the name when
importing from the export domain.  As far as I know you have to start
the import from scratch.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Hi Richard,

Sorry for missing that TMPDIR, I was looking rather than actually reading.

I used the original ova I'd exported from VMWare, and that worked fine
(after fixing perms). The command I ran was:

virt-v2v -x -v -i ova /mnt/import-vm/wvm2.ova -o rhev -os
ovirt-engine:/mnt/export-vm -of qcow2

It returned without error and copied it to the export domain ok. It hasn't
appeared in the list of VMs as yet in the GUI. I guess it is
in the process of doing so? It did show up in the list of importable VMs
under the 'Import VM' tab under
the export domain. I tried importing it from there but it gave me:

2016-07-20 18:27:24,518 INFO
 [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (default
task-317) [27b3ad4b] Lock freed to object
'EngineLock:{exclusiveLocks='[wvm2=,
7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=]',
sharedLocks='[7d40eaee-2f3f-4a4e-8254-4c2c3312ce5c=]'}'

So I guess it is doing the import still.

Cheers,

Campbell


On Wed, Jul 20, 2016 at 4:05 PM, Richard W.M. Jones 
wrote:

> On Wed, Jul 20, 2016 at 03:40:16PM +0100, Cam Mac wrote:
> > Hi Rich,
> >
> >
> > > > >
> > > >
> > > > I can try this but I'm not quite sure how to go about it. The ovf I
> > > created
> > > > via guest-image-ovf-creator is on an NFS mount
>
> Originally you were trying to import OVAs from VMware, which is the
> only source of OVAs we actually test.  If you're trying to import from
> VMware, get VMware to create the OVAs for you using the vSphere Export
> GUI or ovftool:
>
>   http://libguestfs.org/virt-v2v.1.html#ova:-create-ova
>
> > I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
> > ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
> > fails
> >
> > Error is:
> >
> > [root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
> > ovirt-engine:/mnt/export-vm
> > virt-v2v: libguestfs 1.28.1 (x86_64)
> > [   0.0] Opening the source -i ova wvm2.ovf
> > tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
> > virt-v2v: error: could not parse ovf:Name from OVF document
>
> I had a look at guest-image-ovf-creator.py anyway and the problem is
> that this script doesn't put any  section into the OVF
> document at all.  I couldn't keep my eyes open long enough while
> reading the turgid DTMF OVF standards document to find out if this
> section is required or not, but virt-v2v certainly expects it.  (That
> is just the first failure, there may be more.)
>
> Anyway, use an OVA generated by VMware.
>
> > BTW: is there a way of specifying the extraction directory? My first
> > attempt filled up /var/tmp until I found another host
> > that luckily had a big enough partition.
>
> Yes, you can set TMPDIR as mentioned in the manual.
>
> 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Richard W.M. Jones]

On Wed, Jul 20, 2016 at 03:40:16PM +0100, Cam Mac wrote:
> Hi Rich,
> 
> 
> > > >
> > >
> > > I can try this but I'm not quite sure how to go about it. The ovf I
> > created
> > > via guest-image-ovf-creator is on an NFS mount

Originally you were trying to import OVAs from VMware, which is the
only source of OVAs we actually test.  If you're trying to import from
VMware, get VMware to create the OVAs for you using the vSphere Export
GUI or ovftool:

  http://libguestfs.org/virt-v2v.1.html#ova:-create-ova

> I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
> ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
> fails
> 
> Error is:
> 
> [root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
> ovirt-engine:/mnt/export-vm
> virt-v2v: libguestfs 1.28.1 (x86_64)
> [   0.0] Opening the source -i ova wvm2.ovf
> tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
> virt-v2v: error: could not parse ovf:Name from OVF document

I had a look at guest-image-ovf-creator.py anyway and the problem is
that this script doesn't put any  section into the OVF
document at all.  I couldn't keep my eyes open long enough while
reading the turgid DTMF OVF standards document to find out if this
section is required or not, but virt-v2v certainly expects it.  (That
is just the first failure, there may be more.)

Anyway, use an OVA generated by VMware.

> BTW: is there a way of specifying the extraction directory? My first
> attempt filled up /var/tmp until I found another host
> that luckily had a big enough partition.

Yes, you can set TMPDIR as mentioned in the manual.

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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

I tried the GUI first (in 3.6 and later 4.0 after upgrading) and it fails.
I posted to the list about this here:

http://lists.ovirt.org/pipermail/users/2016-June/040442.html

No solution was found so far.

Thanks,

Cam


On Tue, Jul 19, 2016 at 8:51 PM, Richard W.M. Jones 
wrote:

> And I suppose it's worth saying that recent oVirt can import from
> VMware using the oVirt GUI (which works via virt-v2v, but automates
> everything for you).
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Hi Rich,


> > >
> >
> > I can try this but I'm not quite sure how to go about it. The ovf I
> created
> > via guest-image-ovf-creator is on an NFS mount
> > on the engine: do I need to run virt-v2v on one of the nodes? If so, I
> > assume I need to set the output to an export domain.
> > Does '-o local' stick it on the node's VM storage?
>
> Yes, don't use -o local.
>
> virt-v2v has an -o rhev option which will import directly from VMware
> to RHEV or oVirt.  Please see the manual:
>
> http://libguestfs.org/virt-v2v.1.html#convert-from-vmware-to-rhev-m-ovirt
> http://libguestfs.org/virt-v2v.1.html#output-to-rhev
>
>
>
I'm using 'virt-v2v -v -i ova wvm2.ovf -o rhev -os
ovirt-engine:/mnt/export-vm' (my export domain), though unfortunately it
fails

Error is:

[root@kvm-ldn-01 tmp]# virt-v2v -v -x -i ova wvm2.ovf -o rhev -os
ovirt-engine:/mnt/export-vm
virt-v2v: libguestfs 1.28.1 (x86_64)
[   0.0] Opening the source -i ova wvm2.ovf
tar -xzf 'wvm2.ovf' -C '/var/tmp/ova.dEFSqi'
virt-v2v: error: could not parse ovf:Name from OVF document

If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:

  virt-v2v -v -x [...]
[root@kvm-ldn-01 tmp]

I can attach the XML ovf file that is is inside the ovf archive if that is
a help.

BTW: is there a way of specifying the extraction directory? My first
attempt filled up /var/tmp until I found another host
that luckily had a big enough partition.

Thanks,

Cam


> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 19.07.16 20:51, Richard W.M. Jones wrote:
> And I suppose it's worth saying that recent oVirt can import from
> VMware using the oVirt GUI (which works via virt-v2v, but automates
> everything for you).
> 
> Rich.
Richard is right,
you can try to use the import from VMWare to oVirt directly via the oVirt UI
which is under the VMs tab press on the "import" button menu and select VMWare
as the source.

> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines.  Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Richard W.M. Jones]

And I suppose it's worth saying that recent oVirt can import from
VMware using the oVirt GUI (which works via virt-v2v, but automates
everything for you).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Richard W.M. Jones]

On Tue, Jul 19, 2016 at 07:02:24PM +0100, Cam Mac wrote:
> > Try to run virt-v2v -i ova -o local to import the ova to local disk (see
> > the
> > virt-v2v man page for more options) and see if that pass - the errors can
> > be
> > more detailed there (it suppose to reflect the same error that you get in
> > vdsm
> > log)., another options you can do is run virt-v2v in verbose mode (virt-v2v
> > -v).
> >
> 
> I can try this but I'm not quite sure how to go about it. The ovf I created
> via guest-image-ovf-creator is on an NFS mount
> on the engine: do I need to run virt-v2v on one of the nodes? If so, I
> assume I need to set the output to an export domain.
> Does '-o local' stick it on the node's VM storage?

Yes, don't use -o local.

virt-v2v has an -o rhev option which will import directly from VMware
to RHEV or oVirt.  Please see the manual:

http://libguestfs.org/virt-v2v.1.html#convert-from-vmware-to-rhev-m-ovirt
http://libguestfs.org/virt-v2v.1.html#output-to-rhev

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Cam Mac]

Hi Shahar,


> I'm trying to import some .ova images from VMWare that have been copied to
> > a node. In both cases they fail with the error:
> >
> > "Conversion of VM from exteral enironment failed: copy-disk stream closed
> > unexpectedly"
> First you need to look at vdsm log to see more details why it failed.
>
> Here is more detail:

2016-07-14 16:59:01,058 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ConvertOvaVDSCommand]
(pool-7-thread-10) [49ba3bae] START, ConvertOvaVDSCommand(HostName =
kvm-ldn-01, ConvertOvaVDSParameters:{runAsync='true'
, hostId='385dc50a-0617-4e84-9aea-1d9e0de294a5',
ovaPath='/home/export/vm/wvm2.ova', vmName='wvm2',
storageDomainId='9d1fe12c-5c5f-49ad-a875-a735acba2530',
storagePoolId='f351dc97-b524-434c-b14d-c12e04ac4c7d', virtio
2016-07-14 16:59:02,230 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(pool-7-thread-10) [49ba3bae] Correlation ID: 49ba3bae, Call Stack: null,
Custom Event ID: -1, Message: Starting to  convert Vm wvm2
2016-07-14 17:04:44,765 INFO
 [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
(DefaultQuartzScheduler4) [49ba3bae] Conversion of VM from exteral
enironment failed: copy-disk stream closed unexpectedly
2016-07-14 17:04:45,793 ERROR
[org.ovirt.engine.core.bll.exportimport.ConvertOvaCommand]
(DefaultQuartzScheduler2) [43b33ecc] Ending command
'org.ovirt.engine.core.bll.exportimport.ConvertOvaCommand' with failure.
2016-07-14 17:04:45,882 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler2) [43b33ecc] Correlation ID: 49ba3bae, Call Stack:
null, Custom Event ID: -1, Message: Failed to convert Vm wvm2




> >
> > I'm considering using virt-v2v to do the conversion of the .ova, but I'm
> > not sure how to get that into ovirt then.
> >
> > Any suggestions?
>

What I ended up doing was using Joey Boggs's guest-image-ovf-creator.py to
convert the image to the 'correct'
structure and then upload it via engine-image-uploader to my export domain.
It did this, and I can see the files
in the export domain, but I can't import them via the GUI as they don't
appear. Should they? Or should there be
an 'import domain' somewhere?



> Try to run virt-v2v -i ova -o local to import the ova to local disk (see
> the
> virt-v2v man page for more options) and see if that pass - the errors can
> be
> more detailed there (it suppose to reflect the same error that you get in
> vdsm
> log)., another options you can do is run virt-v2v in verbose mode (virt-v2v
> -v).
>

I can try this but I'm not quite sure how to go about it. The ovf I created
via guest-image-ovf-creator is on an NFS mount
on the engine: do I need to run virt-v2v on one of the nodes? If so, I
assume I need to set the output to an export domain.
Does '-o local' stick it on the node's VM storage?


Thanks,

Cam


> >
> > Regards,
> >
> > Cam
>
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of ova failed

[Shahar Havivi]

On 14.07.16 18:14, Cam Mac wrote:
> Hi,
> 
> I'm trying to import some .ova images from VMWare that have been copied to
> a node. In both cases they fail with the error:
> 
> "Conversion of VM from exteral enironment failed: copy-disk stream closed
> unexpectedly"
First you need to look at vdsm log to see more details why it failed.

> 
> (the message above is copied verbatim from the log, including
> the misspellings)
> 
> One of the VMs is a RHEL 6.6 and the other is Windows 7. The import reports
> adding a disk and then running a conversion, then appears to fail about 5
> or 6 minutes into converting the image.
> 
> I'm considering using virt-v2v to do the conversion of the .ova, but I'm
> not sure how to get that into ovirt then.
> 
> Any suggestions?
Try to run virt-v2v -i ova -o local to import the ova to local disk (see the
virt-v2v man page for more options) and see if that pass - the errors can be
more detailed there (it suppose to reflect the same error that you get in vdsm
log)., another options you can do is run virt-v2v in verbose mode (virt-v2v
-v).
> 
> Regards,
> 
> Cam

> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users