Red Hat Bugzilla – Bug 967005
Windows guest agent does not report version for some installed applications
Last modified: 2015-09-22 09:09 EDT
Description of problem:
RHEV-Application Provisioning Tool never contains version, also Microsoft .NET Framework 4 Client Profile, although I can see version of these apps when they are selected in 'Programs and Features' window botton tab.
# vdsClient -s 0 getVmStats 1b4b8755-e40e-403f-a385-ad1a96c04058 | egrep "guestName|appsList"
guestName = JB-W7-X86
appsList = ['Microsoft .NET Framework 4 Client Profile', 'RHEV-Tools 3.2.8', 'RHEV-Serial 3.2.4', 'Microsoft .NET Framework 4 Client Profile', 'RHEV-Spice-Agent 3.2.5', 'RHEV-Agent 3.2.5', 'RHEV-SSO 3.2.4', 'RHEV-USB 3.2.3', 'RHEV-Balloon 3.2.4', 'RHEV-Application Provisioning Tool', 'Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17', 'RHEV-Spice 3.2.3', 'RHEV-Block 3.2.4', 'RHEV-Network 3.2.4']
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install GA
2. check versions of reported apps
some apps do not have version number
include version number as well
we're querying DisplayName. Can you doublecheck or attach the registry file?
You are right, you use DisplayName and not using DisplayVersion. This is even more funny - RHEV-Spice-3.2.3 as DisplayName and 4.9.3 as DisplayVersion (this RHEV-Spice was installed from 3.2.5 iso). So what kind of evidence is version value in DisplayName?... Feel free to tell RHEV-APT owner to change DisplayName for this app.
Lev, what's the reason for the DisplayVersion strings not to correspond with the DisplayName?
Windows Registry Editor Version 5.00
"Publisher"="Red Hat Inc."
"DisplayName"="RHEV-Application Provisioning Tool"
(In reply to Vinzenz Feenstra from comment #3)
> Lev, what's the reason for the DisplayVersion strings not to correspond with
> the DisplayName?
DisplayName doesn't have to include any version information at all.
We include the version information as part of the package name for some packages only for the convenience of our customers, and to make it easier to identify if the correct version of tools is installed as the version displayed will always be based on the version of the RHEV.
For example for RHEV 3.2 all displayed package names (that include version information as part of the package name) will show 3.2.x version, where x is the build number of that specific component for that specific version of RHEV.
DisplayVersion on the other hand is the internal version of the package.
(In reply to Jiri Belka from comment #2)
> You are right, you use DisplayName and not using DisplayVersion. This is
> even more funny - RHEV-Spice-3.2.3 as DisplayName and 4.9.3 as
> DisplayVersion (this RHEV-Spice was installed from 3.2.5 iso). So what kind
> of evidence is version value in DisplayName?... Feel free to tell RHEV-APT
> owner to change DisplayName for this app.
As already explained the version in the DisplayName will always be based on the version of the RHEV. So Windows Guest Tools ISO supplied with RHEV 3.2 will always have version of 3.2.x and all tools installed from it will display version of 3.2.y (where y is package specific for each tool) in it's name as seen in Add/Remove Programs etc.
If requested I can modify APT to work in the same way as well.
So according comments #5 and #6 this is wanted.
If we want the DisplayVersion value also to be reported that would be a new feature and has to be requested as such including changes to the guest agent, vdsm, engine backend and the UI