[Bug 1278595] [NEW] Wrong timeout behavior or output
Karl-Philipp Richter
krichter722 at aol.de
Mon Feb 10 21:49:13 UTC 2014
Public bug reported:
The following result of invokation of ifup is possible in Ubuntu 13.10 with ifupdown 0.7.44ubuntu3:
<code>
time sudo ifup bond1
Waiting for a slave to join bond1 (will timeout after 60s)
No slave joined bond1, continuing anyway
real 0m5.388s
user 0m0.042s
sys 0m0.269s
</pre>
Either the timeout specification of 60s is wrong or the program reads the wrong variable or *something* is very misleading and should be clearified (in the output of the program).
/etc/network/interfaces:
<code>
auto lo
iface lo inet loopback
iface eth0 inet manual
bond-master bond1
bond-primary eth1 eth0
iface eth1 inet manual
bond-master bond1
bond-primary eth1 eth0
iface bond1 inet manual
address 192.168.3.100
netmask 24
bond-slaves eth0 eth1
bond-mode 0
bond-miimon 100
</code>
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
The following result of invokation of ifup is possible in Ubuntu 13.10 with ifupdown 0.7.44ubuntu3:
<code>
time sudo ifup bond1
Waiting for a slave to join bond1 (will timeout after 60s)
No slave joined bond1, continuing anyway
real 0m5.388s
user 0m0.042s
sys 0m0.269s
</pre>
- Either the timeout specification of 60s is wrong or the program reads the wrong variable.
+ Either the timeout specification of 60s is wrong or the program reads the wrong variable or *something* is very misleading and should be clearified (in the output of the program).
/etc/network/interfaces:
<code>
auto lo
iface lo inet loopback
iface eth0 inet manual
- bond-master bond1
- bond-primary eth1 eth0
+ bond-master bond1
+ bond-primary eth1 eth0
iface eth1 inet manual
- bond-master bond1
- bond-primary eth1 eth0
+ bond-master bond1
+ bond-primary eth1 eth0
iface bond1 inet manual
- address 192.168.3.100
- netmask 24
- bond-slaves eth0 eth1
- bond-mode 0
- bond-miimon 100
+ address 192.168.3.100
+ netmask 24
+ bond-slaves eth0 eth1
+ bond-mode 0
+ bond-miimon 100
</code>
--
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/1278595
Title:
Wrong timeout behavior or output
Status in “ifupdown” package in Ubuntu:
New
Bug description:
The following result of invokation of ifup is possible in Ubuntu 13.10 with ifupdown 0.7.44ubuntu3:
<code>
time sudo ifup bond1
Waiting for a slave to join bond1 (will timeout after 60s)
No slave joined bond1, continuing anyway
real 0m5.388s
user 0m0.042s
sys 0m0.269s
</pre>
Either the timeout specification of 60s is wrong or the program reads the wrong variable or *something* is very misleading and should be clearified (in the output of the program).
/etc/network/interfaces:
<code>
auto lo
iface lo inet loopback
iface eth0 inet manual
bond-master bond1
bond-primary eth1 eth0
iface eth1 inet manual
bond-master bond1
bond-primary eth1 eth0
iface bond1 inet manual
address 192.168.3.100
netmask 24
bond-slaves eth0 eth1
bond-mode 0
bond-miimon 100
</code>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1278595/+subscriptions
More information about the foundations-bugs
mailing list