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

Bug 1188216

Summary:	[RFE] - Supply auto-update mechanism for windows.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yaniv Lavi <ylavi>
Component:	mingw-virt-viewer	Assignee:	Default Assignee for SPICE Bugs <rh-spice-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	cfergeau, dblechte, ecohen, gklein, lsurette, marcandre.lureau, michal.skrivanek, rbalakri, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	spice
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-19 13:02:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Spice	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1188212

Description Yaniv Lavi 2015-02-02 11:06:36 UTC

Description of problem:
Currently virt-viewer does not have any auto-updater for windows, so updates can not be automatically applied like with activex plugin. We need this functionality to fully support virt-viewer on windows.

Comment 1 Marc-Andre Lureau 2015-02-02 12:05:04 UTC

(In reply to Yaniv Dary from comment #0)
> Description of problem:
> Currently virt-viewer does not have any auto-updater for windows, so updates
> can not be automatically applied like with activex plugin. We need this
> functionality to fully support virt-viewer on windows.

There is another bug/RFE discussing this already. The current proposal is to use the [virt-viewer] "version" field (available for a while already). This will make the client report an error if the version isn't new enough. Then the client can be updated with RHEVM online help, to help finding this help, we could have a second field, such as "download-page" that would provide a link in the error dialog to open the RHEVM page. And/or another field like "last-installer" to do auto-update.

Comment 2 Yaniv Lavi 2015-02-02 12:19:48 UTC

(In reply to Marc-Andre Lureau from comment #1)
> (In reply to Yaniv Dary from comment #0)
> > Description of problem:
> > Currently virt-viewer does not have any auto-updater for windows, so updates
> > can not be automatically applied like with activex plugin. We need this
> > functionality to fully support virt-viewer on windows.
> 
> There is another bug/RFE discussing this already. The current proposal is to
> use the [virt-viewer] "version" field (available for a while already). This
> will make the client report an error if the version isn't new enough. Then
> the client can be updated with RHEVM online help, to help finding this help,
> we could have a second field, such as "download-page" that would provide a
> link in the error dialog to open the RHEVM page. And/or another field like
> "last-installer" to do auto-update.

Why can't virt-viewer be updated like chrome or firefox in background, so that users will always use the latest?

Comment 3 Marc-Andre Lureau 2015-02-02 12:26:27 UTC

(In reply to Yaniv Dary from comment #2)
> Why can't virt-viewer be updated like chrome or firefox in background, so
> that users will always use the latest?

There is plenty of complicated solutions, nothing that can be done easily, especially because of distributed nature of RHEVM. What I propose should allow auto-update in a quite simple way.

Comment 4 Yaniv Lavi 2015-02-02 12:35:30 UTC

(In reply to Marc-Andre Lureau from comment #3)
> (In reply to Yaniv Dary from comment #2)
> > Why can't virt-viewer be updated like chrome or firefox in background, so
> > that users will always use the latest?
> 
> There is plenty of complicated solutions, nothing that can be done easily,
> especially because of distributed nature of RHEVM. What I propose should
> allow auto-update in a quite simple way.

If you allow the source of the auto update to be modified, it should not be a issue to at least allow user to download from  the dialog without the need to read a kbase. We should make updates easy and lite on the users.

Comment 5 Marc-Andre Lureau 2015-02-02 12:38:33 UTC

(In reply to Yaniv Dary from comment #4)
> If you allow the source of the auto update to be modified, it should not be
> a issue to at least allow user to download from  the dialog without the need
> to read a kbase. We should make updates easy and lite on the users.

what I propose in comment #1.

Comment 6 Yaniv Lavi 2015-02-02 12:50:47 UTC

(In reply to Marc-Andre Lureau from comment #5)
> (In reply to Yaniv Dary from comment #4)
> > If you allow the source of the auto update to be modified, it should not be
> > a issue to at least allow user to download from  the dialog without the need
> > to read a kbase. We should make updates easy and lite on the users.
> 
> what I propose in comment #1.

ok, read again and it sounds reasonable. Can you close this one as dup of the main bug?

Comment 7 David Blechter 2015-02-19 13:02:09 UTC

950248 does not solve the auto-update, so it is not duplicate but another way to give customer option to upgrade to the latest version of both win and rhel spice clients.