PDA

View Full Version : SLES 11 SP4 Double intrface name in ifup calls



ivryakhov
29-Dec-2016, 14:55
Hi,

I've noticed some strange output in syslog according to the ifup script functioning:


Dec 29 08:15:36 linux-s2kv ifup: eth0
Dec 29 08:15:36 linux-s2kv ifup: IP address: ********
Dec 29 08:15:36 linux-s2kv ifup:
Dec 29 08:15:36 linux-s2kv ifup: Handling Index <>:
Dec 29 08:15:36 linux-s2kv ifup: IPADDR = ************
Dec 29 08:15:36 linux-s2kv ifup: PREFIXLEN = 23
Dec 29 08:15:36 linux-s2kv ifup: CHECK_DUPLICATE_IP = no
Dec 29 08:15:36 linux-s2kv ifup-route: eth0 eth0 -o rc onboot
Dec 29 08:15:36 linux-s2kv ifup-route: calling: ip route replace to default via ******** ---> OK
Dec 29 08:15:36 linux-s2kv ifup-route: calling: ip -4 route replace to ******* dev eth0 ---> OK
Dec 29 08:15:36 linux-s2kv ifup-services: eth0 eth0 -o rc onboot
Dec 29 08:15:36 linux-s2kv ifup-services: unknown option rc
Dec 29 08:15:36 linux-s2kv ifup-services: No services to handle for 'eth0 eth0'

I got this using the DEBUG="yes" option in the /etc/sysconfig/network/config file. From this, there are inrorretly called scripts:


Dec 29 08:15:36 linux-s2kv ifup-route: eth0 eth0 -o rc onboot
Dec 29 08:15:36 linux-s2kv ifup-services: eth0 eth0 -o rc onboot

I suppose, this is because of this code in the /sbin/ifup script:


if [ -n "$1" -a "$1" != "-o" ] ; then
CONFIG=$INTERFACE
INTERFACE=$1
fi

and then

...
${SCRIPTNAME}-route $CONFIG $INTERFACE ${OPTIONS:+-o $OPTIONS}
...
scripts/${SCRIPTNAME}-services $CONFIG $INTERFACE ${OPTIONS:+-o $OPTIONS}

Looks like a bug for me, but I can't figure out how to report this to developers?

KBOYLE
29-Dec-2016, 18:46
Looks like a bug for me, but I can't figure out how to report this to developers?

If you have active maintenance you can open a Service Request (https://scc.suse.com/support/requests/new). SUSE Support will have a look and, if it is truly a bug, they will create a bug report. If it is not a bug, they may have a solution for you.

If you don't have maintenance, you can try to file a bug report using Bugzilla (https://bugzilla.suse.com/index.cgi).

A bug report backed by a Service Request that identifies a specific Customer is usually the more effective approach.