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 1498755 - kernel changes in 7.4 prevent to up infiniband port
Summary: kernel changes in 7.4 prevent to up infiniband port
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1499282
TreeView+ depends on / blocked
 
Reported: 2017-10-05 07:29 UTC by Vladimir Benes
Modified: 2018-04-10 13:30 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.8.0-11
Doc Type: Bug Fix
Doc Text:
Previously, when an Infiniband device was disconnected, the kernel in some cases reported a problem that the interface was removed. As a consequence, the NetworkManager's internal state of this device became corrupted. This bug has been fixed, and the NetworkManager service works as expected to provide consistent information about the state of the device.
Clone Of:
: 1499282 (view as bug list)
Environment:
Last Closed: 2018-04-10 13:29:44 UTC
Target Upstream Version:
Embargoed:
thaller: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0778 0 None None None 2018-04-10 13:30:48 UTC

Description Vladimir Benes 2017-10-05 07:29:57 UTC
Description of problem:
I can up infiniband device mlx5_ib0 but not any of it's ports (e.g. mlx5_ib0.8002). This worked in 7.3 correctly, this works correctly even with the latest NM and kernel from 7.3 (514)

Version-Release number of selected component (if applicable):
kernel-3.10.0-693.2.1.el7.x86_64
NetworkManager-1.8.0-10.el7_4.x86_64

How reproducible:
always

Steps to Reproduce:
1.try to up ininiband port

Actual results:
device seems to be connected but NM time outs and says device is still down.

Expected results:
everything should work as before, connection upped, device connected, etc

Additional info:

Comment 1 Beniamino Galvani 2017-10-05 09:44:15 UTC
There are multiple causes of the failures:

 - with RHEL 7.4 kernel NM sometimes fails to delete infiniband
   partitions. It is not clear yet if this is a kernel bug. In NM logs
   there are messages like: "Failed to remove InfiniBand P_Key
   interface 'inf_ib0.8002': unspecified". This alone does not cause
   a test failure.

 - there is a bug in NM that disables all property notifications for a
   device when the situation above happens; as a consequence clients
   have a wrong view of the device state and don't detect the
   successful activation. This is fixed upstream in commit [1].

Currently I'm investigating the first point; anyway I think that the
NM commit should be backported to 7.4 z-stream.

[1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=24a7f88bc56b66745c1e6b9444df8a80125de059

Comment 8 errata-xmlrpc 2018-04-10 13:29:44 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:0778


Note You need to log in before you can comment on or make changes to this bug.