Bug 1723902 - synchronize virtio-win RHEL-7.7 with virtio-win RHEL-8.0.1
Summary: synchronize virtio-win RHEL-7.7 with virtio-win RHEL-8.0.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Danilo de Paula
QA Contact: lijin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-25 16:54 UTC by Danilo de Paula
Modified: 2019-08-06 13:35 UTC (History)
6 users (show)

Fixed In Version: virtio-win-1.9.8-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:34:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2362 0 None None None 2019-08-06 13:35:10 UTC

Description Danilo de Paula 2019-06-25 16:54:09 UTC 
virtio-win follows a straight/single-line development process.

When RHEL-8 appeared, all the development happened on the RHEL-8 branch and those changes are exported verbatin (excluding the drivers that are dropped from RHEL-8) to RHEL-7.

This BZ tracks the synchronization of the virtio-win package into RHEL-7.
Comment 2 Danilo de Paula 2019-06-25 16:55:01 UTC 
We need blocker+ to be able to process virtio-win this late in RHEL-7.7
Comment 3 Danilo de Paula 2019-06-25 16:55:35 UTC 
QA_ACK+, please.
Comment 7 lijin 2019-06-27 00:42:19 UTC 
Check virtio-win-1.9.8-6.el7, all drivers are same as rhel8.0.1 virtio-win package(virtio-win-1.9.8-6.el8).

So change status to verified.
Comment 9 errata-xmlrpc 2019-08-06 13:34:56 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/RHBA-2019:2362
Note You need to log in before you can comment on or make changes to this bug.