Bug 1772740

Summary:	synchronize virtio-win RHEL-7.8 with virtio-win RHEL-8.1.1
Product:	Red Hat Enterprise Linux 7	Reporter:	lijin <lijin>
Component:	virtio-win	Assignee:	Danilo de Paula <ddepaula>
virtio-win sub component:	distribution	QA Contact:	lijin <lijin>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	ddepaula, lmiksik, mtessun
Version:	7.8
Target Milestone:	rc
Target Release:	7.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virtio-win-1.9.10-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-31 09:35:00 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 lijin 2019-11-15 03:25:29 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-12-17 18:22:31 UTC

virtio-win is a package that is always late.
Usually around snapshot 3.

The main update is for rhel-8, so 7-* series arrives a bit later.

We need exception+ to be able to release this.
@martin: can you please grant it?

Comment 4 Danilo de Paula 2019-12-17 18:26:16 UTC

Actually, we need blocker+

Comment 9 lijin 2019-12-20 02:06:49 UTC

check virtio-win-1.9.10-3.el7.noarch, all drivers are synced with virtio-win-1.9.10-3.el8.

Change status to verified.

Comment 11 errata-xmlrpc 2020-03-31 09:35:00 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:0992