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 867273 - IB profile not listed in nm-applet widget
Summary: IB profile not listed in nm-applet widget
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-17 08:03 UTC by Tomas Pelka
Modified: 2013-11-21 21:47 UTC (History)
2 users (show)

Fixed In Version: NetworkManager-0.8.1-48.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 21:47:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
messages (99.77 KB, text/plain)
2013-01-15 11:33 UTC, Tomas Pelka 		no flags Details
[PATCH] Handle InfiniBand devices in nm-applet (RHEL 6.5) (19.73 KB, patch)
2013-05-31 17:38 UTC, Jirka Klimes 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1670 0 normal SHIPPED_LIVE NetworkManager bug fix and enhancement update 2013-11-21 00:39:32 UTC

Description Tomas Pelka 2012-10-17 08:03:42 UTC 
Description of problem:
I configured InfiniBand profile on machine with IB device but not able to connect the profile.

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-37.el6

How reproducible:
100%

Steps to Reproduce:
1. Create IB profile available for all user 
2. manual ipv4 address 
3. put valid MAC address 80:00:00:03:fe:80:00:00:00:00:00:02:00:11:75:00:00:78:b6:64
4. left-click on nm-aplet 
  
Actual results:
No IB profile listed

Expected results:


Additional info:

# nmcli con list
NAME                      UUID                                   TYPE              SCOPE    TIMESTAMP-REAL                    
InfiniBand connection 1   b590d101-a2d0-480f-aad8-92303b4669ac   infiniband        system   never                             
System bnx_1              fdf82711-f0d8-008c-6235-6c4af68dbade   802-3-ethernet    system   Wed 17 Oct 2012 04:00:18 AM EDT   
System bnx_2              7237ce43-6aa2-6d58-afd0-b575f4b9a13d   802-3-ethernet    system   never                             
NAME                      UUID                                   TYPE              SCOPE    TIMESTAMP-REAL

# nmcli con up uuid b590d101-a2d0-480f-aad8-92303b4669ac
Error: No suitable device found: no device found for connection 'InfiniBand connection 1'.

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: bnx_1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether e8:9a:8f:b2:a7:d1 brd ff:ff:ff:ff:ff:ff
3: bnx_2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether e8:9a:8f:b2:a7:d2 brd ff:ff:ff:ff:ff:ff
4: qib_1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc pfifo_fast state UP qlen 256
    link/infiniband 80:00:00:03:fe:80:00:00:00:00:00:02:00:11:75:00:00:78:b6:64 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff

01:00.0 InfiniBand [0c06]: QLogic Corp. IBA7322 QDR InfiniBand HCA [1077:7322] (rev 02)
	Subsystem: QLogic Corp. IBA7322 QDR InfiniBand HCA [1077:7322]
	Flags: bus master, fast devsel, latency 0, IRQ 24
	Memory at ef000000 (64-bit, non-prefetchable) [size=4M]
	Expansion ROM at ef7e0000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 3
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
	Capabilities: [100] Advanced Error Reporting
	Kernel driver in use: ib_qib
	Kernel modules: ib_qib
Comment 1 Jirka Klimes 2012-10-31 13:36:15 UTC 
Can you attach /var/log/message from when you try "nmcli con up"?

What you get for:
$ nmcli dev status
$ nmcli dev list iface qib_1
Comment 2 RHEL Program Management 2012-12-14 08:44:29 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 Tomas Pelka 2013-01-15 11:33:49 UTC 
Created attachment 678727 [details]
messages

(In reply to comment #1)
> Can you attach /var/log/message from when you try "nmcli con up"?
> 
> What you get for:
> $ nmcli dev status

DEVICE     TYPE              STATE       
qib_1      infiniband        disconnected
bnx_1      802-3-ethernet    connected   
bnx_2      802-3-ethernet    unavailable

> $ nmcli dev list iface qib_1

GENERAL.DEVICE:                 qib_1
GENERAL.TYPE:                   infiniband
GENERAL.DRIVER:                 ib_qib
GENERAL.HWADDR:                 80:00:00:03:FE:80:00:00:00:00:00:02:00:11:75:00:00:78:B6:64
GENERAL.STATE:                  disconnected
CAPABILITIES.CARRIER-DETECT:    yes
CAPABILITIES.SPEED:             unknown
Comment 4 Jirka Klimes 2013-01-29 10:39:13 UTC 
(In reply to comment #0)
> # nmcli con up uuid b590d101-a2d0-480f-aad8-92303b4669ac
> Error: No suitable device found: no device found for connection 'InfiniBand
> connection 1'.
> 
The error says there's no IB device available for the connection. I've checked it and that's true, because auto-generated connection has invalid MAC address configured (the one of not available IB device). After changing MAC in the connection profile (or removing the MAC), the command was successful.

As for nm-applet, you are right, it doesn't display InfiniBand connections, because the code for that is missing. I'll post a patch for that.
Comment 8 Jirka Klimes 2013-05-31 17:38:18 UTC 
Created attachment 755326 [details]
[PATCH] Handle InfiniBand devices in nm-applet (RHEL 6.5)

Updated patch that applies to latest RHEL 6.5.
It's been pushed into git and built - NetworkManager-0.8.1-48.el6.
Comment 9 Jirka Klimes 2013-05-31 19:29:15 UTC 
The patch reworked and committed upstream as well:
https://git.gnome.org/browse/network-manager-applet/commit/?id=e80223407978318eea5accf86a87b36c98d20af3
Comment 17 errata-xmlrpc 2013-11-21 21:47:47 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.

http://rhn.redhat.com/errata/RHBA-2013-1670.html
Note You need to log in before you can comment on or make changes to this bug.