Bug 1482419

Summary:	PDB symbol files are missing for some virtio-win binaries
Product:	Red Hat Enterprise Linux 7	Reporter:	lijin <lijin>
Component:	virtio-win	Assignee:	Danilo de Paula <ddepaula>
virtio-win sub component:	distribution	QA Contact:	Virtualization Bugs <virt-bugs>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	ailan, jen, lijin, lmiksik, virt-bugs
Version:	7.4
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	virtio-win-1.9.4-1.el7.src.rpm	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1457845	Environment:
Last Closed:	2018-04-10 06:31:38 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:
Bug Depends On:	1457845
Bug Blocks:

Comment 1 Jeff Nelson 2017-08-18 17:25:27 UTC

Description of problem:
A subset of virtio-win binaries doesn't have their symbol files persisted anywhere. Not even in the raw prewhql build. They are lost forever after a build is completed and the build machine recycled.


--- Additional comment from Ladi Prosek on 2017-07-14 02:12:44 EDT ---

Fixed in commits:

https://github.com/virtio-win/kvm-guest-drivers-windows/commit/c9a3abccc854a8e1c7223b3ee6d1ebff0a6940cc
https://github.com/virtio-win/kvm-guest-drivers-windows/commit/9286da9e4a98712ca64aa3040ee204f8caf9ad92

I'll update virtio-win packaging scripts once a raw build with these fixes is available.


--- Additional comment from lijin on 2017-08-17 04:41:03 EDT ---

[...]

I will clone this bug to distribution sub-component as it affects virtio-win packaging as well

Comment 5 lijin 2018-01-18 01:57:47 UTC

Check in virtio-win-1.9.4-1.el7.noarch, these pdb files are not existing, so change status to verified.

Thanks

Comment 7 errata-xmlrpc 2018-04-10 06:31:38 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-2018:0657