[Bug 950409] Re: ifup fails but returns 0
Stéphane Graber
stgraber at stgraber.org
Fri Mar 9 00:01:04 UTC 2012
Marking as Won't fix at it's currently done by design.
ifupdown 0.7 when released will check for script return codes (in this
case the bridge-utils script) and will fail as you'd expect.
It's currently not the case because during the week or so where we had
that code turned on in Ubuntu we've seen quite a few packages completely
exploding as they were expecting ifupdown to disregard their return
code.
The actual change will most likely happen around 12.10 or when Debian
gets around to reviewing all the existing ifupdown scripts and making
sure they return sane return codes.
** Changed in: ifupdown (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/950409
Title:
ifup fails but returns 0
Status in “ifupdown” package in Ubuntu:
Won't Fix
Bug description:
This is from the packaged xen script 'network-bridge'.
do_ifup() {
#if [ $1 != "${netdev}" ] || ! ifup $1 ; then
if [ -n "$addr_pfx" ] ; then
# use the info from get_ip_info()
ip addr flush $1
ip addr add ${addr_pfx} dev $1
fi
ip link set dev $1 up
[ -n "$gateway" ] && ip route add default via ${gateway}
#fi
}
I needed to comment out the encasing 'if' because ifup exits 0 even
though it fails. It throws a RETLINK error due to an ip existing on
the interface, but $? = 0. This causes the rest to fail and the
bridge is not properly established.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/950409/+subscriptions
More information about the foundations-bugs
mailing list