Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
InfiniBand network device doesn't exist on the installed system, although it was available and used during the installation - the system was installed via this interface.
[root@localhost ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 14:18:77:6e:cb:3e brd ff:ff:ff:ff:ff:ff
altname enp1s0f0
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 14:18:77:6e:cb:3f brd ff:ff:ff:ff:ff:ff
altname enp1s0f1
4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 14:18:77:6e:cb:40 brd ff:ff:ff:ff:ff:ff
altname enp2s0f0
5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 14:18:77:6e:cb:41 brd ff:ff:ff:ff:ff:ff
altname enp2s0f1
6: enp4s0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 24:8a:07:56:b8:34 brd ff:ff:ff:ff:ff:ff
[root@localhost ~]#
After installing the rdma-core package and restart, the device is available and properly configured:
[root@localhost ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
.
.
.
7: ibp130s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc mq state UP group default qlen 256
link/infiniband 00:00:0e:4e:fe:80:00:00:00:00:00:00:24:8a:07:03:00:49:d7:5c brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
inet 172.31.0.122/24 brd 172.31.0.255 scope global dynamic noprefixroute ibp130s0f0
valid_lft 3584sec preferred_lft 3584sec
inet6 fe80::268a:703:49:d75c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
8: ibp130s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc mq state UP group default qlen 256
link/infiniband 00:00:15:15:fe:80:00:00:00:00:00:01:24:8a:07:03:00:49:d7:5d brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
[root@localhost ~]#
Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220203.0
anaconda-34.25.0.25-1.el9
How reproducible:
1 out of 1 attempt
Steps to Reproduce:
1. Run installation via an InfiniBand device (with ip=ibp130s0f0:dhcp on the kernel command line)
2. Finish the installation and reboot to the installed system
Actual results:
InfiniBand devices don't exist.
Expected results:
InfiniBand devices exist and properly configured.
Additional info:
Workaround is to install the rdma-core package after the installation (or add the package to the %packages section in the kickstart file).
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 (anaconda bug fix and enhancement update), 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-2022:7977
Description of problem: InfiniBand network device doesn't exist on the installed system, although it was available and used during the installation - the system was installed via this interface. [root@localhost ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 14:18:77:6e:cb:3e brd ff:ff:ff:ff:ff:ff altname enp1s0f0 3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 14:18:77:6e:cb:3f brd ff:ff:ff:ff:ff:ff altname enp1s0f1 4: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 14:18:77:6e:cb:40 brd ff:ff:ff:ff:ff:ff altname enp2s0f0 5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 14:18:77:6e:cb:41 brd ff:ff:ff:ff:ff:ff altname enp2s0f1 6: enp4s0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 24:8a:07:56:b8:34 brd ff:ff:ff:ff:ff:ff [root@localhost ~]# After installing the rdma-core package and restart, the device is available and properly configured: [root@localhost ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 . . . 7: ibp130s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc mq state UP group default qlen 256 link/infiniband 00:00:0e:4e:fe:80:00:00:00:00:00:00:24:8a:07:03:00:49:d7:5c brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff inet 172.31.0.122/24 brd 172.31.0.255 scope global dynamic noprefixroute ibp130s0f0 valid_lft 3584sec preferred_lft 3584sec inet6 fe80::268a:703:49:d75c/64 scope link noprefixroute valid_lft forever preferred_lft forever 8: ibp130s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2044 qdisc mq state UP group default qlen 256 link/infiniband 00:00:15:15:fe:80:00:00:00:00:00:01:24:8a:07:03:00:49:d7:5d brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff [root@localhost ~]# Version-Release number of selected component (if applicable): RHEL-9.0.0-20220203.0 anaconda-34.25.0.25-1.el9 How reproducible: 1 out of 1 attempt Steps to Reproduce: 1. Run installation via an InfiniBand device (with ip=ibp130s0f0:dhcp on the kernel command line) 2. Finish the installation and reboot to the installed system Actual results: InfiniBand devices don't exist. Expected results: InfiniBand devices exist and properly configured. Additional info: Workaround is to install the rdma-core package after the installation (or add the package to the %packages section in the kickstart file).