Bug 1548407

Summary:	[CodeChange] get rid of SpiceVersion.txt and its handling
Product:	[oVirt] ovirt-engine	Reporter:	Tomas Jelinek <tjelinek>
Component:	Frontend.WebAdmin	Assignee:	Alexander Wels <awels>
Status:	CLOSED WONTFIX	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.1.2	CC:	bugs
Target Milestone:	---	Keywords:	CodeChange
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-10 00:56:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2018-02-23 12:34:15 UTC

Description of problem:
Back in the days when the SPICE client has been opened using ActiveX or XPI plugins, the ActiveX one supported a parameter called "version" which was a way how to update the plugin to the newest version.

Today, for the same thing we use the RemoteViewerSupportedVersions and RemoteViewerNewerVersionUrl from vdc_options.

But, we still ship the SpiceVersion.txt and we still load it on frontend and are parsing the version out of it. It would be nice to get rid of it completely.

Comment 1 Greg Sheremeta 2018-10-10 00:56:04 UTC

Unfortunately we don't have capacity to work on this.