Bug 1724445

Summary:	Do not require glusterfs on i686
Product:	Red Hat Enterprise Linux Advanced Virtualization	Reporter:	Pavel Hrdina <phrdina>
Component:	libvirt	Assignee:	Pavel Hrdina <phrdina>
Status:	CLOSED ERRATA	QA Contact:	Han Han <hhan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.1	CC:	chhu, dyuan, hhan, jdenemar, rbalakri, xuzhang, yalzhang
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-5.4.0-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1722668	Environment:
Last Closed:	2019-11-06 07:17:15 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:	1722668
Bug Blocks:

Description Pavel Hrdina 2019-06-27 06:43:48 UTC

+++ This bug was initially created as a clone of Bug #1722668 +++

Description of problem:

The 6.0 build of glusterfs dropped i686 packages, which means libvirt cannot be built on RHEL 8.1.0 anymore.

Version-Release number of selected component (if applicable):

libvirt-5.4.0-1.module+el8.1.0+3513+32057e89

How reproducible:

100%

Steps to Reproduce:
1. build libvirt on RHEL 8.1.0

Actual results:

i686 build fails with
No matching package to install: 'glusterfs-api-devel >= 3.4.1'
No matching package to install: 'glusterfs-devel >= 3.4.1'

Expected results:


Additional info:

We're only interested in libvirt libraries on i686 so building with gluster is not needed.

Comment 3 Han Han 2019-09-18 06:40:13 UTC

No functional change for libvirt. Since not i686 arch release in rhel8, no changes to other arches. Mark it as verified

Comment 5 errata-xmlrpc 2019-11-06 07:17:15 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:3723