Red Hat Bugzilla – Bug 1211933
Add rpm wrapper for RHEV-M appliance
Last modified: 2016-03-09 16:43:46 EST
Description of problem: To simplify the delivery of the rhevm appliance we should add an rpm wrapper which can be used to install the appliance image on a host using yum/rhn. This needs to be synced with 1211532
All referenced patches have been merged, shouldn't this be in modified?
There is still some unfinished work in distgit whcih needs more handling, once that is done this can be moved to MODIFIED
rpm wrapper builds are now available here: http://jenkins.ovirt.org/job/ovirt-appliance-engine_master_create-rpms-el7-noarch_merged/ The layout and interface between he-setup and the appliance location has been discussed in bug 1211532.
The builds are available. Testing depends on the bugs depending on this. Once they are merged this feature can be fully tested. Testing scope needs to be defined.
Fabian, it seems the brew link is now deleted. Could you please share a new brew link and move to ON_QA once it is ready?
Verification steps: the rpm should contains two files: a description file under /etc/ovirt-hosted-engine/*-appliance.conf and the OVA The description file structure is: description=<Descriptive text> version=<appliance release info> path=<ova file path> sha1sum=<ova file sha1sum> please check that the version number and the description look coherent, the path is correct and the sha1sum matches the OVA file.
Verified with: rhevm-appliance-20151022.1-1.el6ev.noarch # cat /etc/ovirt-hosted-engine-setup/10-appliance.conf description=The RHEV-M Appliance image (OVA) version=20151022.1-1.el6ev path=/usr/share/ovirt-engine-appliance/rhevm-appliance-20151022.1-1.el6ev.ova sha1sum= ova file path is correct but sha1sum is empty.
(In reply to Gonza from comment #11) > ova file path is correct but sha1sum is empty. This is an issue cause hosted-engine-setup will ensure that the OVA file will match that.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Isn't this a blocker to first beta? No HE with appliance.
(In reply to Yaniv Dary from comment #14) > Isn't this a blocker to first beta? No HE with appliance. Yes, it is. Blocker flag is in place and I've escalated it via email too
(In reply to Yaniv Dary from comment #14) > Isn't this a blocker to first beta? No HE with appliance. looks like blocker+ hasn't been triggered by bot / rule engine. please fix manually.
I can(In reply to Sandro Bonazzola from comment #17) > (In reply to Yaniv Dary from comment #14) > > Isn't this a blocker to first beta? No HE with appliance. > > looks like blocker+ hasn't been triggered by bot / rule engine. > please fix manually. I can't. (In reply to Gil Klein from comment #16) > (In reply to Yaniv Dary from comment #14) > > Isn't this a blocker to first beta? No HE with appliance. > Yes, it is. Blocker flag is in place and I've escalated it via email too So why change the target milestone? I means that the target is beta 2 on not beta 1.
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://access.redhat.com/errata/RHBA-2016:0385