View Issue Details

IDProjectCategoryView StatusLast Update
0017851CentOS-7rdmapublic2020-11-19 05:41
Reportersstcdev 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Platformx86_64OSCentOS-7OS Version7.8.2003
Product Version7.8-2003 
Target VersionFixed in Version 
Summary0017851: ifup-ib in rdma-core-22.4-1.el7.x86_64 always shows error messages in setting device MTU wrongly.
Descriptionifup-ib in rdma-core-22.4-1.el7.x86_64 or later always shows error messages wrongly
 like
[root@sandy01 network-scripts]# ifup ib0
ERROR : [/etc/sysconfig/network-scripts/ifup-ib] Error setting device ib0 MTU to 1500, using HW default.

What's wrong is only the error messages.
MTU is set as specified successfully.

[root@sandy01 network-scripts]# ip address show ib0
4: ib0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 256
    link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:00:02:c9:03:00:f9:2a:51 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
    inet 192.168.17.130/24 brd 192.168.17.255 scope global ib0
       valid_lft forever preferred_lft forever



[root@sandy01 ~]# cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)
[root@sandy01 ~]# rpm -qf /etc/sysconfig/network-scripts/ifup-ib
rdma-core-22.4-1.el7.x86_64
Steps To Reproduceifup ib0

static IP address for ib0 is better.
Because DHCP logic is more complicated.


[root@sandy01 network-scripts]# ifdown ib0
[root@sandy01 network-scripts]# ifup ib0
ERROR : [/etc/sysconfig/network-scripts/ifup-ib] Error setting device ib0 MTU to 1500, using HW default.
[root@sandy01 network-scripts]# ip address show ib0
4: ib0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 256
    link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:00:02:c9:03:00:f9:2a:51 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
    inet 192.168.17.130/24 brd 192.168.17.255 scope global ib0
       valid_lft forever preferred_lft forever
[root@sandy01 network-scripts]# cat ifcfg-ib0
CONNECTED_MODE=no
TYPE=InfiniBand
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=static
IPADDR=192.168.17.130
PREFIX=24
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=ib0
UUID=9b380ae6-ee07-4ab2-8bd6-78c5a109153e
DEVICE=ib0
ONBOOT=yes
ZONE=trusted
MTU=1500
NOZEROCONF=yes
Additional InformationSince rdma-core-22.4-1.el7.x86_64 in 7.8.2003,
/etc/sysconfig/network-scripts/ifup-ib] in rdma-core-22.4-1.el7.x86_64 was modified.

- We want to focus on
 secstion for setting ib0's MTU.
    127 if [ -n "${MTU}" ]; then
    128 ip link set dev ${DEVICE} mtu ${MTU}
    129 if [ "$?" ]; then
    130 net_log $"Error setting device ${DEVICE} MTU to ${MTU}, using HW default."
    131 fi
    132 fi

return value should be treated more carefully like
[root@sandy01 network-scripts]# diff ifup-ib.sstc ifup-ib
129c129
< if [ "$?" -gt 0 ]; then
---
> if [ "$?" ]; then

- even return value is 0, the if [$? ] is true.


[root@sandy01 ~]# cat eval0.sh
#!/bin/bash
if [ 1 ]; then
  echo true if 1
fi
if [ 0 ]; then
  echo true even if 0
fi
[root@sandy01 ~]# bash eval0.sh
true if 1
true even if 0


- We also checked following RPMs and ifup-ib in them are identical.
cent7.8/rdma-core-22.4-2.el7_8.x86_64.rpm
cent7.8/rdma-core-22.4-4.el7_8.x86_64.rpm
cent7.9/rdma-core-22.4-5.el7.x86_64.rpm
TagsNo tags attached.
abrt_hash
URL

Activities

ManuelWolfshant

ManuelWolfshant

2020-11-13 14:43

manager   ~0037896

Please update your system to CentOS 7.9. If the issue still persist, , as CentOS is a rebuild of the sources used to create RHEL and aims to reproduce RHEL bug for bug and feature for feature, please submit your request to Redhat via bugzilla.redhat.com and if/when RH accepts it and incorporates it into RHEL and releases a patched version, then CentOS will pick it up automatically.
For easier tracking, please crosslink this bug with the one opened at bugzilla.redhat.com.
sstcdev

sstcdev

2020-11-19 05:41

reporter   ~0037936

We installed RHEL7.9 and reproduced the same issue.
We submitted the same issue
 to
  https://bugzilla.redhat.com/show_bug.cgi?id=1899397

Issue History

Date Modified Username Field Change
2020-11-13 09:58 sstcdev New Issue
2020-11-13 14:43 ManuelWolfshant Note Added: 0037896
2020-11-19 05:41 sstcdev Note Added: 0037936