[Expired for ifupdown (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: ifupdown (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
** Changed in: ifupdown (Ubuntu Xenial)
Status: Confirmed => Incomplete
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
@newsuk-platform, are you still having this problem? If not, let's
close this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1636708
Title:
ifup -a does not start
@ddstreet I opened a separate ticket as requested a while ago. Some eyes
on it would be very welcome. It's bug 1759573
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
** Changed in: ifupdown (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1636708
Title:
ifup -a
> networking.service spawns ifup@.services in parallel with no ordering
information
no, networking.service calls ifup -a, it doesn't spawn ifup@ services.
ifup -a doesn't bring up interfaces in parallel, it brings them up
sequentially as ordered in the /etc/networking/interface file(s).
However,
The fixes in vlan package are insufficient, as networking.service spawns
ifup@.services in parallel with no ordering information and therefore
systemd is free to process them in a racy manner. At boot ifup@.services
are racing with networking.service and can result in a deadlock as you
have
First, I believe the original description of this case shows it's the
same problem (or same fix at least) as bug 1573272 - the vlan is racing
with its raw device bond to come up. The fix in that bug should address
this problem, by forcing the bond interface to always come up first
(it's forced
We upgraded to the vlan 1.9-3.2ubuntu1.16.04.3 package and our
networking broke horribly in a very similar way.
Let me start with our networking configuration. Two slaves, a bond and a
vlan on top of that bond:
auto eno1
iface eno1 inet manual
mtu 1500
bond-master bond1
bond-primary
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
> Why would bond0 get created when loading the bonding module?
Because the default module parameter max_bonds for bonding module is 1,
meaning create one bond upon bond module loading.
I have since hit similar issue with networkd where bonding module would
be autoprobed, bond0 created, and
** Changed in: ifupdown (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1636708
Title:
ifup -a does not start dependants last,
On Tue, May 9, 2017 at 10:32 AM, Dimitri John Ledkov wrote:
> Maybe this is easier to read.
>
> root@xnox-iad-nr5:~# journalctl -o short-monotonic -u ifup@bond0.service
> -- Logs begin at Tue 2017-05-09 10:57:18 UTC, end at Tue 2017-05-09
> 15:22:34 UTC. --
> [
Maybe this is easier to read.
root@xnox-iad-nr5:~# journalctl -o short-monotonic -u ifup@bond0.service
-- Logs begin at Tue 2017-05-09 10:57:18 UTC, end at Tue 2017-05-09 15:22:34
UTC. --
[6.740201] xnox-iad-nr5 systemd[1]: Started ifup for bond0.
[6.750333] xnox-iad-nr5 sh[1184]:
** Also affects: ifupdown (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1636708
Title:
ifup -a does not
@ Chris Pitchford
Could you please try below, and let us know if that works for you, with your
proposed workaround reverted?
The reason being, is that with a generator we should be able to create these
orderings using the original / unmodified eni files as generated by installers
/ were in use
Not quite.
On boot, there are multiple ways that ifup is called, and effectively it
races with itself.
In my case I have two vlans, on top of a bond, of two NICs. By the time
networking.service is called, the two NICs are present.
networking.service is essentially `ifup -a`, it looks at the eni
On Mon, May 8, 2017 at 9:06 AM, Dimitri John Ledkov
wrote:
> I thought we have systemd hotplugging as well, can we not generate
>
I'm not sure what this means
> depedencies that ifup@bond0.5.service Wants= and After=
> ifup@bond0.service? and prevent all of these
I thought we have systemd hotplugging as well, can we not generate
depedencies that ifup@bond0.5.service Wants= and After=
ifup@bond0.service? and prevent all of these locks?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
21 matches
Mail list logo