Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 836659

Summary:	[RFE] Add notification to Admin Portal when a newer version is available for RHEV-M/RHEV-H/vdsm/tools
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marina Kalinin <mkalinin>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED DUPLICATE	QA Contact:	yeylon <yeylon>
Severity:	low	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	alonbl, byount, iheim, lpeer, meverett, oourfali, rbalakri, srevivo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	sgrinber: Triaged+
Hardware:	Unspecified
OS:	Linux
Whiteboard:	infra
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-21 09:13:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1157368, 1157369
Bug Blocks:

Description Marina Kalinin 2012-06-29 20:42:12 UTC

Add notification to Admin Portal when a newer version is available for RHEV-M/RHEV-H/vdsm/tools.

Customers are not upgrading their RHEV environments most of the time because they are not aware about new versions available. Since they work on RHEV via Admin Portal it should be a good place to put a notification on it when a newer version is available.

Location: either on top of Admin Portal or as a notification message each time before login.

Comment 1 Itamar Heim 2013-01-07 08:11:40 UTC

alon - is there an easy way of doing this with all the new otopi/yum-api work?

Comment 2 Alon Bar-Lev 2013-01-07 12:42:29 UTC

(In reply to comment #1)
> alon - is there an easy way of doing this with all the new otopi/yum-api
> work?

Yes, no problem to do this, just confirmed.

Question: what is the method? I think best is to send email notification...

If not, we can have crond script to use engine-config to put something as option... Not sure if this is better than file based trigger.

Comment 9 Alon Bar-Lev 2013-01-14 12:35:20 UTC

commit 5d7ca9210bdd498083a1ddfd3a7367075d4f8c60
Author: Alon Bar-Lev <alonbl>
Date:   Mon Jan 14 14:20:02 2013 +0200

    packaging: periodically check if ovirt-engine upgrade available
    
    Using yum API and version lock plugin disabled check if there is a newer
    version of ovirt-engine package.
    
    If there is, create a trigger file at:
    
     /var/cache/ovirt-engine/engine-upgrade.available
    
    It is the responsibility of the engine to monitor this trigger and clean
    when act upon.
    
    COMPONENTS
    
    engine-upgrade-check.py
    	A simple utility to check if update is available.
    	It will echo AVAILABLE if it finds update.
    
    engine-upgrade-check.cron
    	cron.d script to be executed daily. Uses
    	engine-upgrade-check.py to detect update and creates the
    	trigger.
    
    Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=836659
    Signed-off-by: Alon Bar-Lev <alonbl>
    Change-Id: I76019e8ccc3e77d70b812bd9187c0cbdbb3f4f07

http://gerrit.ovirt.org/#/c/10976/

Comment 12 Itamar Heim 2013-03-01 14:36:33 UTC

*** Bug 916891 has been marked as a duplicate of this bug. ***

Comment 13 Oved Ourfali 2015-04-21 09:13:55 UTC


*** This bug has been marked as a duplicate of bug 1016839 ***