*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
> @ddstreet here's how I reproduced:
ok thnx, I will set that up and try it to reproduce
> You are correct: the proper way to bring up the bond is to bring up
> it's slaves. Running ifup on the bond just h
@ddstreet here's how I reproduced: I created a VirtualBox VM with Xenial
and 3 interfaces: enp0s3 and enp0s8 on an internal network, enp0s9 on a
bridge to my LAN). Then I applied each of the 4 configurations below and
ran "ifup -a". Try it and you'll see the same behavior.
You are correct: the pro
@tom-verdaat I'm temporarily removing this as dup, because I can't
reproduce your error on xenial, or maybe I don't understand the specific
error you're talking about.
> # ifup bond1
> Waiting for a slave to join bond1 (will timeout after 60s)
This isn't new; trying to do this even with an edited
** This bug is no longer a duplicate of bug 1701023
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759573
Title:
vlan on to
*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
Totally support marking this as a duplicate. As long as we get this fix
pushed a.s.a.p. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
@paelzer yep will do
@tom-verdaat if you don't mind, i'll just dup this bug as @paelzer
suggested and work the fix in bug 1701023. Sorry about this regression.
** This bug has been marked a duplicate of b
Thanks Dan for pointing to the right solution.
Would you make this bug a dup then and add tasks for xenial (this is what this
bug is reported as) if needed to the target bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Got right on it! Tested your PPA version on the same testcases and it
works perfectly. Indeed the same issue and the same type of resolution.
Your ifquery is more elegant though, so definitely go with that!
Would love to see this released and pushed a.s.a.p. because this is
breaking our production
Yep, I think this is similar or the same as bug 1701023, the original
vlan-ordering-ifup-call that i had to add for bug 1573272 is sometimes
causing ifupdown locking issues, although ifupdown is supposed to do
separate locking for each device.
Anyway, I have a test fix that's similar to yours - bu
Been doing some troubleshooting and we think we've found the fix for
this issue:
The script /etc/network/if-pre-up.d/vlan contains the following section
of code starting at line 62:
if [ ! -e "/sys/class/net/$IFACE" ]; then
# Try ifup for the raw device, if it fails then bring it up directly
10 matches
Mail list logo
