Description of problem:
It can not setup hosted engine through OVA from TUI. It reports that the downloaded image is neither an OVA nor an ISO.
Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.1-20150609.0
ovirt-node-plugin-hosted-engine-0.2.0-15.0.el7ev.noarch
rhevm-appliance-20150421.0-1.x86_64.rhevm.ova
How reproducible:
Steps to Reproduce:
1. Clean install rhev-hypervisor7-7.1-20150609.0
2. File the OVA URL to point the rhevm appliance from brew.
3. Check the rhevm ova file's type
Actual results:
1. After step2, it will reports the downloaded image is neither an OVA nor an ISO.
2. After step3, the output is as follows.
# file /data/ovirt-hosted-engine-setup/rhevm-appliance-20150421.0-1.x86_64.rhevm.ova
/data/ovirt-hosted-engine-setup/rhevm-appliance-20150421.0-1.x86_64.rhevm.ova: POSIX tar archive (GNU)
While the remote ova format is gzip as follows.
# file rhevm-appliance-20150421.0-1.x86_64.rhevm.ova
rhevm-appliance-20150421.0-1.x86_64.rhevm.ova: gzip compressed data, was "/tmp/koji/tasks/9978/9019978/ou", last modified: Wed Apr 22 03:04:21 2015, max compression
Expected results:
1. It should start the hosted engine setup with OVA file.
Additional info:
No such issue when using the same OVA file in rhev-hypervisor6-6.7-20150609.0.
Test version:
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch
ovirt-node-plugin-hosted-engine-0.3.0-1.el7ev.noarch
Test steps:
1. Install rhev-hypervisor7-7.2-20151025.0.el7ev with TUI
2. Enable network
3. File 'Engine ISO/OVA URL for download' field with the accessable rhevm ova file
4. Check the rhevm ova file's type
Test result:
1. # file rhevm-appliance-20151022.1-1.x86_64.rhevm.ova
rhevm-appliance-20151022.1-1.x86_64.rhevm.ova: gzip compressed data, was "/tmp/koji/tasks/1217/10001217/output_image/tmpGCnLxO/ova", last modified: Thu Oct 22 18:16:07 2015, max compression
So the ova which is downloaded by rhevh is gzip now. This issue is fixed in ovirt-node-plugin-hosted-engine-0.3.0-1.el7ev.noarch. Change the status to verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0378.html