RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1771814 - QEMU Guest Agent's version is not correct which is still the old one.
Summary: QEMU Guest Agent's version is not correct which is still the old one.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Basil Salman
QA Contact: xiagao
URL:
Whiteboard:
Depends On:
Blocks: 1779885
TreeView+ depends on / blocked
 
Reported: 2019-11-13 03:26 UTC by xiagao
Modified: 2022-05-11 09:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1779885 (view as bug list)
Environment:
Last Closed: 2020-02-04 12:27:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:
knoel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-29497 0 None None None 2022-05-11 09:40:53 UTC

Description xiagao 2019-11-13 03:26:28 UTC
Description of problem:
QEMU Guest Agent's version is still 100.0.0 which should be 101.0.0

Version-Release number of selected component (if applicable):
qemu-ga-win-101.0.0.1-4.el7ev.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1.boot up windows guest and install qemu-ga-win msi installer
2.check qemu-ga-win version from "Programs and Features"
3.

Actual results:
QEMU guest agent version: 100.0.0

Expected results:


Additional info:
it should be 101.0.0

Comment 2 Basil Salman 2019-11-14 15:17:01 UTC
Can you please test this build ?
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1010674

Comment 3 xiagao 2019-11-15 02:33:02 UTC
(In reply to Basil Salman from comment #2)
> Can you please test this build ?
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1010674

Verify this bug with this build.
from host:
# nc -U /tmp/helloworld2
{"execute":"guest-info"}
{"return": {"version": "101.0.0",

from guest:
It's 101.0.0 from "Programs and Features".

Comment 4 xiagao 2019-11-15 05:29:47 UTC
mingw-qemu-ga-win-101.0.0-5.el7ev	
mingw-qemu-ga-win-101.0.0.1-4.el7ev	

Hi,
I see the rpm package version is changed from 101.0.0.1 to 101.0.0, do you want to use 3 sets of digits later.
From the pkg history[1], it is changed from 3 sets to 4 sets,and now it's changed to 3 again.

[1] https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=63849

Comment 5 Basil Salman 2019-11-17 09:11:01 UTC
I changed the rpm package version from 4 sets to 3 sets again in order to be consistent with qemu-ga version.

Comment 7 errata-xmlrpc 2020-02-04 12:27:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0351


Note You need to log in before you can comment on or make changes to this bug.