RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1494607 - [RHEL-7.5] rdma-core: update to upstream release v15
Summary: [RHEL-7.5] rdma-core: update to upstream release v15
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rdma-core
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jarod Wilson
QA Contact: zguo
URL:
Whiteboard:
: 1384905 1397710 1454966 1455131 1456544 1457682 1458321 1458741 1458748 (view as bug list)
Depends On: 1494610
Blocks: 1400036 1411448 1413149 1429983 1432225 1442258 1449793 1451930 1452236 1454965 1461180 1461182 1469186 1478971 1522983
TreeView+ depends on / blocked
 
Reported: 2017-09-22 15:31 UTC by Jarod Wilson
Modified: 2018-04-10 17:51 UTC (History)
17 users (show)

Fixed In Version: rdma-core-15-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 17:48:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0954 0 None None None 2018-04-10 17:51:04 UTC

Description Jarod Wilson 2017-09-22 15:31:16 UTC 
Description of problem:
We tend to rebase the rdma kernel subsystem every release, and the rdma userspace (and thus rdma-core) needs to be updated in sync with that. We're targeting 4.14 upstream kernel code for Red Hat Enterprise Linux 7.5, which means we need the latest rdma-core as well, so we're updating to v15.
Comment 2 Jarod Wilson 2017-09-22 15:43:04 UTC 
*** Bug 1454966 has been marked as a duplicate of this bug. ***
Comment 3 Jarod Wilson 2017-09-22 15:43:06 UTC 
*** Bug 1384905 has been marked as a duplicate of this bug. ***
Comment 4 Jarod Wilson 2017-09-22 15:43:18 UTC 
*** Bug 1455131 has been marked as a duplicate of this bug. ***
Comment 5 Doug Ledford 2017-09-22 15:43:25 UTC 
Note: This release significantly changes how the rdma-core package loads RDMA modules.  In particular, it enables kernel module autoloading instead of a static kernel module load via the rdma.service systemd service.  This will need significant testing to make sure that the update doesn't break working systems.
Comment 6 Jarod Wilson 2017-09-22 15:43:44 UTC 
*** Bug 1457682 has been marked as a duplicate of this bug. ***
Comment 7 Jarod Wilson 2017-09-22 15:44:02 UTC 
*** Bug 1458321 has been marked as a duplicate of this bug. ***
Comment 8 Jarod Wilson 2017-09-22 15:45:54 UTC 
(In reply to Doug Ledford from comment #5)
> Note: This release significantly changes how the rdma-core package loads
> RDMA modules.  In particular, it enables kernel module autoloading instead
> of a static kernel module load via the rdma.service systemd service.  This
> will need significant testing to make sure that the update doesn't break
> working systems.

Looks like there's a corresponding udev patch we'll need as well:
  commit 5570d7f95612 ("Support 'rdma' as a ListenNetlink= argument (#6626)")
Comment 9 Jarod Wilson 2017-09-22 15:46:21 UTC 
Er, no udev, I meant systemd.
Comment 12 Jarod Wilson 2017-09-22 18:57:02 UTC 
*** Bug 1397710 has been marked as a duplicate of this bug. ***
Comment 14 ocrdma-dev.pdl 2017-09-28 12:43:06 UTC 
hardware/configurations supported:
 -Broadcom NetXtreme-C and NetXtreme-E BCM573xx and BCM574xx 10/20/25/40/50/100 Gbps Ethernet Network Controllers

Setup, teardown, and any other configuration commands required to prepare for feature tests:
 - Setup 2 hosts with Broadcom's adaptors
 - Connection the link through Back to Back
 - Make sure "yum groupinstall Infiniband" succeeds.
 - Make sure bnxt_en.ko is loaded.
 - Assign IP addresses to interfaces on both the hosts
 - Make sure bnxt_re.ko is loaded.
 - make sure rdma-core rpm is installed.
 - ibv_devinfo should list bnxt_reX devices.
 - Run following command(s) to verify functionality:

Server:
rping -s -d -v -a <ip of server bnxt interface>
Client:
rping -c -d -v -a <ip of server bnxt interface>

 - Run other RDMA capable test tools like
ib_*_bw and ib_*_lat set of tools in RDMA_CM and socket mode to report bandwith and latency numbers.
Comment 16 Andre Beausoleil 2017-12-21 15:42:47 UTC 
*** Bug 1456544 has been marked as a duplicate of this bug. ***
Comment 18 IBM Bug Proxy 2018-02-21 07:10:54 UTC 
------- Comment From mgrf.com 2018-02-21 02:06 EDT-------
This is verified on R 7.5 snapshots - set to verified   thx
Comment 20 Jarod Wilson 2018-04-06 14:04:13 UTC 
*** Bug 1458741 has been marked as a duplicate of this bug. ***
Comment 21 Jarod Wilson 2018-04-06 14:06:25 UTC 
*** Bug 1458748 has been marked as a duplicate of this bug. ***
Comment 23 errata-xmlrpc 2018-04-10 17:48: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/RHEA-2018:0954
Note You need to log in before you can comment on or make changes to this bug.