Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1483995

Summary:	packaging: use rdma-core(-devel) instead of ibverbs, rdmacm; disable rdma on armv7hl
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	packaging	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1483996 1483997 (view as bug list)		Environment:
Last Closed:	2017-12-08 17:39:07 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:
Bug Blocks:	1483996, 1483997

Description Kaleb KEITHLEY 2017-08-22 12:42:20 UTC

Description of problem:

Starting in Fedora 26 the rdma-core package replaces various (lib)ibverbs and (lib)rdmacm packages.

Also apparently rdma never actually worked (even if ibverbs and rdmacm packages were built) for armv7hl. The new rdma-core excludes armv7hl.

See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WJHXQ3G6H7UMVERDCMUXBYDJTFABTGW3/ and https://bugzilla.redhat.com/show_bug.cgi?id=1483278

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Even though rdma-core dates back to Fedora 26 I tentatively plan to make the switch effective with Fedora 27 and later; rdma-core has Provides: (and Obsoletes:) for all the ibverbs and rdmacm packages which is why we haven't noticed this before now.

Comment 1 Worker Ant 2017-08-22 14:23:33 UTC

REVIEW: https://review.gluster.org/18088 (packaging: use rdma-core(-devel) instead of ibverbs, rdmacm) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)

Comment 2 Kaleb KEITHLEY 2017-08-22 14:50:04 UTC

Seems it's been in RHEL since Feb 2017 as well. RHEL 7.3?

Comment 3 Worker Ant 2017-08-22 21:12:30 UTC

COMMIT: https://review.gluster.org/18088 committed in master by Niels de Vos (ndevos) 
------
commit 2c1ddc55d1de154e072710fee18652977c832fa9
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Tue Aug 22 10:21:48 2017 -0400

    packaging: use rdma-core(-devel) instead of ibverbs, rdmacm
    
    Also disable rdma on armv7hl.
    
    Starting in Fedora 26 the rdma-core package replaces various
    (lib)ibverbs and (lib)rdmacm packages.
    
    Also apparently rdma never actually worked (even if ibverbs and
    rdmacm packages were built) for armv7hl. The new rdma-core excludes
    armv7hl.
    
    See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WJHXQ3G6H7UMVERDCMUXBYDJTFABTGW3/
    and https://bugzilla.redhat.com/show_bug.cgi?id=1483278
    
    Even though rdma-core dates back to Fedora 26 this only makes the
    switch to rdma-core effective with Fedora 27 and later; rdma-core has
    Provides: (and Obsoletes:) for all the ibverbs and rdmacm packages
    which is why we haven't noticed this before now.
    
    Change-Id: I3cd4f2becb465569b2c8e5514d28c9adff534d26
    BUG: 1483995
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: https://review.gluster.org/18088
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Niels de Vos <ndevos>

Comment 4 Shyamsundar 2017-12-08 17:39:07 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report.

glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/