** Changed in: ifupdown (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337873
Title:
ifupdown initialization problems caused by race condition
To manage
Thank you for the report sirswa.
I have analyzed your config and came to some conclusions. You may want to
consider using one of the approaches below:
* giving up on bonding and replacing it with bridging in STP mode (please
consult the man pages at http://manpages.ubuntu.com/cgi-bin/search.py?q
Hi Dariusz
Thanks for looking into it. The config looks like mine.
p3p1 interfaces are Mellanox CX PCI cards and could it be due to modules are
not loaded yet when bonding starts?
I have upgraded ifupdown to 0.7.47.2ubuntu4.3 version to get more logs.
I have attached
service --status-all output
@sirswa I tried to reproduce this in my environment - unsuccessfully.
I created a similar config - please take a look at my it for reference:
http://paste.ubuntu.com/15129899/
Maybe you could spot a difference that I overlooked.
This could mean that this change may be interfering with something
Hi all
I upgraded ifenslave and ifupdown to 2.4ubuntu1.2 and 0.7.47.2ubuntu4.3
respectively. After reboot, the bonding did not come up correctly; mtu
were set wrongly (default to 1500), default gateway was not set,
nameserver information were not set in /etc/resolv.conf
After downgrading ifupdown
Thanx a lot, all is working now. My bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337873
Title:
ifupdown initialization problems caused by race condition
To manage notifications about this bu
Hello Max,
My guess (supported by a test I made in a test environment) is the cause of the
problem are those lines under iface bond0:
pre-ip ifup eth2
pre-up ifup eth3
Those are most probably causing a deadlock, since the new release aims to fix
the race condition causing the or
Hello!
I am running Ubuntu 14.04.3 LTS.
This update introduces problem in my setup, adapted to old behavior:
auto eth2
iface eth2 inet manual
bond-master bond0
up ip link set $IFACE txqueuelen 1
auto eth3
iface eth3 inet manual
bond-master bond0
up ip link set
** Changed in: ifupdown (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337873
Title:
ifupdown initialization problems caused by race condit
This bug was fixed in the package ifupdown - 0.7.47.2ubuntu4.3
---
ifupdown (0.7.47.2ubuntu4.3) trusty; urgency=medium
[ Martin Pitt ]
* Fix ifquery crash if interface state file does not exist yet.
(Closes: #810779, LP: #1532722)
-- Dariusz Gadomski Tue, 12 Jan 2016
11:05
This bug was fixed in the package ifenslave - 2.4ubuntu1.2
---
ifenslave (2.4ubuntu1.2) trusty; urgency=medium
* Don't depend on /run/network/ifstate. (LP: #1337873)
-- Dariusz Gadomski Thu, 01 Oct 2015
11:30:24 +0200
** Changed in: ifenslave (Ubuntu Trusty)
Status: Fix
Since I've added the fix to bug 1532722 and after several days of
testing I did not observe any other issues on Trusty and Wily I'm
tagging this as verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ub
** Changed in: ifupdown (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: ifupdown (Ubuntu Wily)
Status: In Progress => Fix Committed
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a m
I sponsored the updated trusty/wily patches, thanks!
** Changed in: ifupdown (Ubuntu Trusty)
Status: Fix Committed => In Progress
** Changed in: ifupdown (Ubuntu Wily)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bug
Updated SRU proposal for Trusty (fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548430/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification because
New SRU proposal for Wily (with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548431/+files/wily_ifupdown_0.7.54ubuntu1.2.debdiff
--
You received this bug notification because you are
** Patch removed: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
** Patch removed: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifu
** Summary changed:
- Precise, Trusty, Utopic - ifupdown initialization problems caused by race
condition
+ ifupdown initialization problems caused by race condition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
18 matches
Mail list logo