Description of problem: ~~~ ... [ INFO ] Detecting available oVirt engine appliances [ INFO ] No engine appliance image is available on your system. Using an oVirt engine appliance could greatly speed-up ovirt hosted-engine deploy. You could get oVirt engine appliance installing ovirt-engine-appliance rpm. Please specify path to OVF archive you would like to use [None]: http://10.34.63.204/pub/tmp/rhevm-appliance-20160620.0-1.el7ev.ova [ ERROR ] The specified file does not exists [ ERROR ] The specified OVF archive is not a valid OVF archive. Please specify path to OVF archive you would like to use [None]: ... ~~~ IMO it would be good to have the setup be able to download OVF archive from URI instead of having it locally. This is especially case for (old) RHEVH. Version-Release number of selected component (if applicable): 1.3.7.2 How reproducible: 100% Steps to Reproduce: 1. hosted-engine --deploy 2. pur http URL for ovf archive 3. Actual results: the setup doesn't know how to work with http URL Expected results: nice to have Additional info:
qemu-img already supports the http backend so this could be an easy goal: [stirabos@t440s ~] $ qemu-img info --output json http://10.34.63.204/pub/tmp/rhevm-appliance-20160620.0-1.el7ev.ova { "virtual-size": 1969667072, "filename": "json:{\"driver\": \"raw\", \"file\": {\"url\": \"http://10.34.63.204/pub/tmp/rhevm-appliance-20160620.0-1.el7ev.ova\", \"driver\": \"http\"}}", "format": "raw" }
(In reply to Simone Tiraboschi from comment #1) > qemu-img already supports the http backend so this could be an easy goal: Question is if this is relevant since we want to introduce ova rpm install during the hosted-engine deployment. If we still see value in this, I'm ok with it.
(In reply to Sandro Bonazzola from comment #2) > (In reply to Simone Tiraboschi from comment #1) > > qemu-img already supports the http backend so this could be an easy goal: > > Question is if this is relevant since we want to introduce ova rpm install > during the hosted-engine deployment. > If we still see value in this, I'm ok with it. If we are able to install the ova rpm on the fly I don't see any value here except a marginal space gain due to the lack rpm extraction at setup time.
Please provide a customization default for download.
*** Bug 1320971 has been marked as a duplicate of this bug. ***
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Works for me on these components on host: ovirt-engine-appliance-4.1-20161202.1.el7.centos.noarch ovirt-imageio-common-0.5.0-0.201611201242.gitb02532b.el7.centos.noarch ovirt-setup-lib-1.1.0-0.0.master.20161107100014.gitb73abeb.el7.centos.noarch ovirt-hosted-engine-setup-2.1.0-0.0.master.20161130101611.gitb3ad261.el7.centos.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch qemu-kvm-rhev-2.6.0-28.el7_3.2.x86_64 ovirt-host-deploy-1.6.0-0.0.master.20161107121647.gitfd7ddcd.el7.centos.noarch rhev-release-4.0.6-6-001.noarch sanlock-3.4.0-1.el7.x86_64 mom-0.5.8-1.el7ev.noarch ovirt-imageio-daemon-0.5.0-0.201611201242.gitb02532b.el7.centos.noarch vdsm-4.18.999-1020.git1ff41b1.el7.centos.x86_64 ovirt-vmconsole-host-1.0.4-1.el7ev.noarch ovirt-release41-pre-4.1.0-0.0.beta.20161201085255.git731841c.el7.centos.noarch ovirt-hosted-engine-ha-2.1.0-0.0.master.20161130135331.20161130135328.git3541725.el7.centos.noarch libvirt-client-2.0.0-10.el7_3.2.x86_64 ovirt-vmconsole-1.0.4-1.el7ev.noarch Linux version 3.10.0-514.2.2.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Nov 16 13:15:13 EST 2016 Linux 3.10.0-514.2.2.el7.x86_64 #1 SMP Wed Nov 16 13:15:13 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) I've received as follows on my environment: [ ERROR ] No engine appliance image is available on your system. The oVirt engine appliance is now required to deploy hosted-engine. You could get oVirt engine appliance installing ovirt-engine-appliance rpm. Do you want to install ovirt-engine-appliance rpm? (Yes, No) [Yes]: [ INFO ] Stage: Environment packages setup [ INFO ] Installing the oVirt engine appliance [ INFO ] Yum Status: Downloading Packages [ INFO ] Yum Downloading: ovirt-engine-appliance-4.1-20161202.1.el7.centos.noarch.rpm 89 M(11%) Probably this is not an error, as its more like a warning here, as nothing is actually wrong. Can we change the error to warning? Moving this bug to verified as it works as designed.
At that point is an error since you cannot simply ignore: you have to fix downloading the appliance or to abort.