*** This bug is a duplicate of bug 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 hangs as you have already
> established. This is an entirely different bug I guess

indeed, i've thought about trying to fix that behavior in the past, but
as you can see touching ifupdown and everything around it is rather
dangerous, and the bonds work during bootup, so I never bothered.
Hopefully with Bionic everyone will move to using systemd-networkd...?

> Just to summarize: it is a duplicate of the other bug and it is fixed
by your patch!

Ok, well that is good - I'm still trying to reproduce because I want to
make sure I'm covering everything correctly.  I have to make sure the
original bug 1573272 remains "fixed", but also fix this bug, and not
introduce any other regressions.

Also I understand this has been breaking things for you, but because of
the fragile nature of ifupdown (and the various if-pre-up.d scripts
added onto it), I don't want to rush this fix, so I'd like to review
things more deeply and do more testing next week, before starting an SRU
for this.  You are welcome to use my ppa package in the meantime, if
that helps you, and the versioning on the PPA build is such that any
official vlan package should replace my ppa build, when this is fixed in
the future.

I'll re-mark this as a duplicate, and continue the work in the other


** This bug has been marked 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.

  vlan on top of untagged network won't start

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to