Bug 1664422

Summary:	perl-Sys-Virt fails to build when building a module
Product:	Red Hat Enterprise Linux Advanced Virtualization	Reporter:	Danilo de Paula <ddepaula>
Component:	perl-Sys-Virt	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED ERRATA	QA Contact:	Dan Zheng <dzheng>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.0	CC:	chhu, dyuan, jdenemar, jen, jsuchane, knoel, mtessun, xuzhang, yalzhang
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	perl-Sys-Virt-4.10.0-1.module+el8+2684+e7e789b9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-29 16:04:59 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 Danilo de Paula 2019-01-08 17:46:34 UTC

Description of problem:
perl-Sys-Virt fails to build when building virt:8.0.0 module

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19710904

Comment 3 Daniel Berrangé 2019-01-09 16:08:25 UTC

The problem is due to libvirt in virt:8.0.0 being rebased on v4.10.0, while perl-Sys-Virt was left on the older version v4.5.0.  There was a change in libvirt 4.10.0 that broke the test suite for perl-Sys-Virt, due to stricter data validation.  We simply need to rebase to 4.10.0 for perl-Sys-Virt to match libvirt.

Comment 8 Dan Zheng 2019-02-28 02:19:35 UTC

Check below builds are successful

perl-Sys-Virt-4.10.0-1.module+el8+2684+e7e789b9
perl-Sys-Virt-5.0.0-1.module+el8+2734+e0d8b77e

And run acceptance test on perl-Sys-Virt-5.0.0-1.module+el8+2734+e0d8b77e, result is OK.

Comment 11 errata-xmlrpc 2019-05-29 16:04:59 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:1293