Bug 963501
Summary: | [RFE] ability to select version of virt-viewer to deploy to clients | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Bryan Yount <byount> |
Component: | spice-activex-win | Assignee: | Arnon Gilboa <agilboa> |
Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.3 | CC: | acathrow, byount, cfergeau, dblechte, ecohen, iheim, jkt, lyarwood, Rhev-m-bugs, ssekidde |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-18 12:14:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bryan Yount
2013-05-16 01:21:06 UTC
isn't this just downgrading the rpm back to the working version on the engine? (In reply to Itamar Heim from comment #2) > isn't this just downgrading the rpm back to the working version on the > engine? I can see Bryan documented this in the attached kbase but I think the customer behind the now closed case that prompted this RFE wanted a more automatic solution. Bryan can you confirm? (In reply to Lee Yarwood from comment #3) > (In reply to Itamar Heim from comment #2) > > isn't this just downgrading the rpm back to the working version on the > > engine? > > I can see Bryan documented this in the attached kbase but I think the > customer behind the now closed case that prompted this RFE wanted a more > automatic solution. Bryan can you confirm? we can't do automatic things from engine about rpm's being deployed at system level? (In reply to Itamar Heim from comment #2) > isn't this just downgrading the rpm back to the working version on the > engine? Yes, for most Linux admins this would be an easy downgrade of the RPM but there's also the issue of manually editing the SpiceVersion.txt file to make the version number 1 higher than it was before so that you trick IE into thinking there's an update when it's really a downgrade. (In reply to Lee Yarwood from comment #3) > I can see Bryan documented this in the attached kbase but I think the > customer behind the now closed case that prompted this RFE wanted a more > automatic solution. Bryan can you confirm? Lee, that is correct. The idea here is we're selling RHEV to people that aren't necessarily Linux-savvy and it would be good if we could make the product as friendly and easy to use as possible. This would help the novice admin roll back a version of virt-viewer if the latest one, for example, started crashing on all their client machines or something. As we move to MSI + MIME deployment this can be handled by administrators cleanly in a way that we can't with AX + XPI (In reply to Andrew Cathrow from comment #7) > As we move to MSI + MIME deployment this can be handled by administrators > cleanly in a way that we can't with AX + XPI I have a question for you, though, Andy. What about my customer where most of their users are outside the environment and not under the company's control? How will the spice-client be distributed then? Will it still be hosted on the RHEV-M? It'd just be an MSI so could be hosted anywhere, even emailed. |