@zagarin please see bug 1701023
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage notifications about
> In vlan ifupdown pre-up script, instead of calling ip link up for raw
device before creating vlan interface, do a full ifup for raw device.
Doing so introduces another kind of problem. Consider the following
setup:
auto eno1
iface eno1 inet dhcp
auto eno1.101
iface eno1.101 inet manual
@tom-verdaat, your problem sounds like a new issue separate from bug
1636708 - can you please open a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not
@Tom
Can you verify that downgrading to 1.9-3.2ubuntu1.16.04.2 and rebooting
makes the problem disappear, and that upgrading again to
1.9-3.2ubuntu1.16.04.3 and rebooting makes the problem appear again? You
can grab the older debs from
https://launchpad.net/ubuntu/+source/vlan/+publishinghistory.
Found this bug ticket while troubleshooting a networking issue with
bonding and vlans after upgrading the vlan package. Reported it here:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/11
Any chance this change caused that issue?
--
You received this bug notification
This bug was fixed in the package vlan - 1.9-3ubuntu10.4
---
vlan (1.9-3ubuntu10.4) trusty; urgency=medium
* Don't trust ifup return code, as it returns 0 on failure; call ip link
set up after ifup to force vlan raw device up. (LP: #1573272)
-- Dan Streetman
This bug was fixed in the package vlan - 1.9-3.2ubuntu2.17.04.2
---
vlan (1.9-3.2ubuntu2.17.04.2) zesty; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
This bug was fixed in the package vlan - 1.9-3.2ubuntu2.16.10.2
---
vlan (1.9-3.2ubuntu2.16.10.2) yakkety; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
This bug was fixed in the package vlan - 1.9-3.2ubuntu1.16.04.3
---
vlan (1.9-3.2ubuntu1.16.04.3) xenial; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
Testing on trusty, same (except interface names, e.g. ens7 -> eth1, etc)
e/n/i config as comment 61. I could not use the systemd change from
comment 8, since trusty uses upstart, and I could not find the proper
place in upstart code to introduce a delay to more easily reproduce the
bug, but I did
Hello Zachary, or anyone else affected,
Accepted vlan into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/vlan/1.9-3ubuntu10.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage notifications
** Tags removed: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage
** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond
** Tags removed: verification-needed
** Tags added: verification-needed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces
** Changed in: vlan (Ubuntu Trusty)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces
Additional debdiff for trusty, as ifup return code on trusty can't be
trusted.
** Patch added: "lp1573272v3-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4889447/+files/lp1573272v3-trusty.debdiff
--
You received this bug notification because you are
Unfortunately, verification for this fails on trusty.
tl;dr:
The patches so far work to fix this on x/y/z/a, but trusty will need an
additional patch to unconditionally call 'ip link set up', since the
return code of 'ifup' on trusty can't be trusted. I'll attach that
trusty debdiff.
Long
Testing on xenial, same e/n/i config and ifup@.service change:
$ dpkg -l | grep vlan
ii vlan 1.9-3.2ubuntu1.16.04.1
$ ip r
default via 192.168.122.1 dev ens3
default via 1.2.3.1 dev ens7.100 metric 1000 onlink
default via 4.5.6.1 dev bond0 metric 2000 onlink
Testing on yakkety, same e/n/i config and systemd ifup@.service
modification:
$ dpkg -l | grep vlan
ii vlan 1.9-3.2ubuntu2
$ ip r
default via 192.168.122.1 dev ens3
default via 1.2.3.1 dev ens7.100 metric 1000 onlink
default via 4.5.6.1 dev bond0 metric
Testing on zesty, same e/n/i configuration as artful, same
/lib/systemd/system/ifup@.service modification to trigger bug:
$ dpkg -l | grep vlan
ii vlan 1.9-3.2ubuntu2
$ ip r
default via 192.168.122.1 dev ens3
default via 1.2.3.1 dev ens7.100 metric 1000
Testing on artful:
I created a virtual guest with extra interfaces to use for testing, all
connected to a single host bridge, which are named ens7-12 in the guest.
I added e/n/i configuration to test both for the original problem for
this bug (vlan on bond loses gateway) as well as the bug
Hello Zachary, or anyone else affected,
Accepted vlan into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu2.17.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
and a explanation has been publicly made at the attention of all SRU
members on Freenode (#ubuntu-release) to explain them the context of
this new upload to overwrite/replace the actual -proposed package(s)
having the regression.
** Tags removed: verification-needed
--
You received this bug
Hi dan,
v2 debdiffs has been uploaded in the upload queue for all affected
stable releases.
- Eric
** Changed in: vlan (Ubuntu Zesty)
Status: Fix Committed => In Progress
** Changed in: vlan (Ubuntu Yakkety)
Status: Fix Committed => In Progress
** Changed in: vlan (Ubuntu
Manually applied the fixup delta on a host which had the issue (not
having a base device configured) and it comes up with network/vlan
working (just a pre-proposed hint but I am not sure I can do a timely
verification with the proposed package).
--
You received this bug notification because you
This bug was fixed in the package vlan - 1.9-3.2ubuntu4
---
vlan (1.9-3.2ubuntu4) artful; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
-- Dan
** Tags removed: sts-sru-done
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To
** Changed in: vlan (Ubuntu Artful)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through
Attached v2 patches for artful and SRU releases; instead of changing the
vlan if-pre-up.d script to use only ifup instead of ip link up, change
the script to use both; first try ifup for the vlan raw device, then if
that fails (e.g. because ifupdown has no configuration for the vlan raw
device)
** Patch added: "lp1573272v2-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4885915/+files/lp1573272v2-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272v2-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4885911/+files/lp1573272v2-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272v2-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4885914/+files/lp1573272v2-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272v2-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4885913/+files/lp1573272v2-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272v2-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4885912/+files/lp1573272v2-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note, this change breaks the system configuration where an ifupdown vlan
is configured, but the raw device is not configured in ifupdown. I'm
working on an additional patch fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Zachary, or anyone else affected,
Accepted vlan into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu2.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags removed: patch sts-sru-needed
** Tags added: sts-sru-done
** Changed in: vlan (Ubuntu Zesty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: vlan (Ubuntu Yakkety)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: vlan (Ubuntu Xenial)
This bug was fixed in the package vlan - 1.9-3.2ubuntu3
---
vlan (1.9-3.2ubuntu3) artful; urgency=medium
* In vlan ifupdown pre-up script, instead of calling ip link up for
raw device before creating vlan interface, do a full ifup for raw
device. Otherwise, if raw device
** Also affects: vlan (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Trusty)
smoser, stgraber, you guys have done some ifupdown and/or vlan
uploads/changes before...can either of you review and/or sponsor this
into artful?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
> The reentrancy is a red flag for me. Is there an existing example of ifup
> being
> called from an if-pre-up.d script?
yes, the ifenslave if-pre-up.d script does call ifup for all its slave
interfaces, i.e.:
# Bring up slave if it is the target of an allow-bondX stanza.
# This is usefull to
Hi Dan,
I'm not particularly familiar with ifupdown. The reentrancy is a red
flag for me. Is there an existing example of ifup being called from an
if-pre-up.d script?
I think it would be best to get a review from someone more familiar with
this area before upload.
--
You received this bug
** Patch removed: "lp1573272-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff
** Patch removed: "lp1573272-yakkety.debdiff"
** Patch added: "lp1573272-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4881559/+files/lp1573272-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Robie, you uploaded the last couple vlan pkg changes, can you
review/sponsor this change also?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for
updated release debdiffs to correct version numbers, and add debdiff for
artful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces
** Patch added: "lp1573272-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4881560/+files/lp1573272-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4881558/+files/lp1573272-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: sts-sponsor
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To
Thanks a lot Dan and Jared.
As this node is intended to be used on a critical production service,
I'll rather wait for the patch rolling from ubuntu repos.
In order to be sure that it will fix the issue, I've patch the script
file manually and it working fine.
--
You received this bug
Right, this isn't fixed yet. I'll try to get this into Artful asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through
@Gael from what I can tell the fix has not been released based on this
bug status is still 'in progress'.
I'm running Ubuntu 16.04 with vlan 1.9-3.2ubuntu1 and it still contains
the 'ip link set up dev $IF_VLAN_RAW_DEVICE' on line 63 of /etc/network
/if-pre-up.d/vlan . You can modify the file
This doesn't seems to be a kernel issue as I'm having the exact same
issue with a fresh Ubunutu 16.04.2 LTS using a 4.4.0 kernel serie and a
vlan 1.9.3 package on top of the bonding interface.
I can confirm that this bug is also impacting the dns resolution as even
when the vlan interface is
@Dan, I filled a bug about it, seems to be an issue with kernel 4.10:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679823
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
> I don't know if it's related but since the I'm using this vlan package
I have this issue:
it's hard to tell just from that output, what does your interfaces
file(s) look like?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Only few of them still down:
# ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno49: mtu 9000 qdisc mq master
bond0 state UP mode
I don't know if it's related but since the I'm using this vlan package I
have this issue:
Apr 04 17:08:30 compute001 ifup[2396]: Waiting for a slave to join bond0 (will
timeout after 60s)
Apr 04 17:08:30 compute001 ifup[2396]: ifquery: recursion detected for
interface bond0 in pre-up phase
Apr
The patch fixes the issue for me as well. Thanks !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage
** Changed in: vlan (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To
I created a PPA with fixed vlan packages:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1573272
** Tags removed: bot-comment patch xenial
** Tags added: sts-sponsor
** Tags added: patch
** Also affects: vlan (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127
The attachment "lp1573272-trusty.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
** Description changed:
- Expectation: After reboot, route for default gateway specified on
- bonded interface is installed according to "gateway x.x.x.x" (where
- x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or
- files sourced per /etc/network/interfaces
+ [Impact]
+
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127
** Bug watch added: Debian Bug tracker #859127
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850618/+files/lp1573272-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850617/+files/lp1573272-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1573272-yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850619/+files/lp1573272-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this as 'invalid' for ifupdown, as the problem is in the vlan
package's script.
** Also affects: vlan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vlan (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: vlan (Ubuntu)
Importance:
Thanks everyone, I'll work on getting the patch upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To
The patch fixes the issue for me as well. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage
The patch fixes the issue for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage
confirm, the patch is working for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage
Seems OK for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
To manage notifications about this bug go to:
This patch to the vlan pre-up script should fix this bug, can someone
who can easily reproduce it please update your system and retest to
verify it fixes the bug? You can just hand-edit your vlan script as
shown, to replace the call to ip to instead do a full ifup on the raw
device.
---
Ok I've reproduced this by introducing a delay by changing
/lib/systemd/system/ifup@.service
-ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifup --allow=auto %I; \
+ExecStart=/bin/sh -ec '/usr/bin/test %I == bond0 && echo found bond0 && sleep
3 ; ifup --allow=hotplug %I; ifup --allow=auto %I;
I set up a default xenial vm with 2 extra interfaces, and configured
them with exactly the config you listed in the description, and left it
in a reboot loop checking for the default gateway each time, and it
hasn't seen the problem at all, after hours of rebooting. Is there a
something else
Any idea if an upstream fix will be applied on Xenial ?
It's a very annoying issue :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond
As a workaround, you can do the following (using the original report's
config as an example):
# systemctl edit ifup@bond0.3000
Add the following and save the file:
[Unit]
After=ifup@bond0.service
Then, let's add Type=oneshot to the ifup@ template so that the above
After= actually has some
Able to replicate this very reliably with any bonded interface on Xenial
Default Gateway (configured in e/n/i) is never set on boot, but always
set with any interface raise thereafter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i think this affects more than just "bond" interfaces, and more than
just the gateway setting from /etc/network/interfaces. i think dns-
settings are also affected as experienced on 4 of my systems. note bug
#1628552
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through reboot
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
** Tags added: xenial
** Package changed: ubuntu => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573272
Title:
default gateway route not installed for bond interfaces through
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
85 matches
Mail list logo