[ovirt-devel] Manageiq ova upload is failing

[Tomas Jelinek]

On Wed, Jan 4, 2017 at 9:39 AM, Piotr Kliczewski <piotr.kliczewski at gmail.com
> wrote:

> On Wed, Jan 4, 2017 at 6:51 AM, Michal Skrivanek <mskrivan at redhat.com>
> wrote:
> >> On 03 Jan 2017, at 23:59, Piotr Kliczewski <piotr.kliczewski at gmail.com>
> wrote:
> >>
> >> All,
> >>
> >> I want to upload manageiq ova from [1] when I attempted to do it I see:
> >>
> >> on the engine side:
> >>
> >> 2017-01-03 23:43:59,318+01 ERROR
> >> [org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-1)
> >
> > You're falling for the confusing trap we created:)
> > OVA in oVirt is for vmware ova conversion, not for importing ovirt
> > native-like images. For that you need to use the old and cumbersome
> > flow of export/import via export domain
>
> I looked for it initially and noticed that ovirt-image-uploader is not
> there in 4.1.
>
> Is there any other way to do it?
>

you should be able to go to webadmin to disks tab and upload it from there.


>
> >
> >> [33a1d8b5-8cec-4b00-9a35-ee9f1d9635b2] Exception:
> >> org.ovirt.engine.core.common.errors.EngineException: EngineException:
> >> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> >> VDSGenericException: VDSErrorException: Failed to GetOvaInfoVDS, error
> >> = Error parsing ovf information: no memory size, code = -32603 (Failed
> >> with error unexpected and code 16)
> >>        at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(
> VdsHandler.java:118)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.
> runVdsCommand(VDSBrokerFrontendImpl.java:33)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.QueriesCommandBase.runVdsCommand(
> QueriesCommandBase.java:242)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.GetVmFromOvaQuery.
> getVmInfoFromOvaFile(GetVmFromOvaQuery.java:24)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.GetVmFromOvaQuery.
> executeQueryCommand(GetVmFromOvaQuery.java:20)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(
> QueriesCommandBase.java:110)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.dal.VdcCommandBase.execute(
> VdcCommandBase.java:33)
> >> [dal.jar:]
> >>        at org.ovirt.engine.core.bll.executor.
> DefaultBackendQueryExecutor.execute(DefaultBackendQueryExecutor.java:14)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.
> java:579)
> >> [bll.jar:]
> >>        at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:547)
> >> [bll.jar:]
> >>
> >> on the vdsm side:
> >>
> >> 2017-01-03 23:43:58,437 ERROR (jsonrpc/0) [jsonrpc.JsonRpcServer]
> >> Internal server error (__init__:552)
> >> Traceback (most recent call last):
> >>  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line
> >> 547, in _handle_request
> >>    res = method(**params)
> >>  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line
> >> 198, in _dynamicMethod
> >>    result = fn(*methodArgs)
> >>  File "/usr/share/vdsm/API.py", line 1493, in getExternalVmFromOva
> >>    return v2v.get_ova_info(ova_path)
> >>  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 226, in
> get_ova_info
> >>    _add_general_ovf_info(vm, root, ns, ova_path)
> >>  File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 1225, in
> >> _add_general_ovf_info
> >>    raise V2VError('Error parsing ovf information: no memory size')
> >> V2VError: Error parsing ovf information: no memory size
> >>
> >> Is our code not parsing correctly or manageiq guys publish not correct
> file?
> >>
> >> I am using:
> >> ovirt-engine
> >> Version     : 4.1.0
> >> Release     : 0.3.beta2.20161221085908.el7.centos
> >> vdsm
> >> Version     : 4.18.999
> >> Release     : 1218.gitd36143e.el7.centos
> >>
> >> Thanks,
> >> Piotr
> >>
> >>
> >> [1] http://manageiq.org/download/
> >> _______________________________________________
> >> Devel mailing list
> >> Devel at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >>
> >>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170104/3f1f8ebf/attachment.html>