Comment 32 for bug 1701023

> We migrated from separate files in /etc/networking/interfaces.d to just declaring
> everything in the single /etc/networking/interfaces file. This overcomes a lot of
> issues with regards to bringing interfaces up in the proper order and "ifup -a"
> now works perfectly again

great.

> (a) to have bonds come up correctly you absolutely have to define slaves before the
> bond master and the primary slave before secondary slaves in the configuration file,
> and (b) to have a vlan come up correctly define its raw device before the vlan device.

yep, I'm pretty sure this is how ifupdown has always behaved. However, please do feel free to open a bug, as it should work better and not require specific ordering like this (I just can't promise it will get fixed soon). Also, if it ever worked in the past that you know of, it's more likely to be fixed, so do note that if you open a new bug.

> bringing bonds up correctly at boot does not

it should - can you please downgrade to the vlan version 1.9-3.2ubuntu1.16.04.1 (assuming you're on Xenial), and if it still fails there, please open a new bug. If it doesn't fail there, then let me know in this bug, as it's a regression from my changes.

You can download the older vlan package from here:
https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu1.16.04.1

click on the arch you're using under 'Builds' to get to the arch-specific page with binary deb links, e.g. for amd64:
http://launchpadlibrarian.net/289303685/vlan_1.9-3.2ubuntu1.16.04.1_amd64.deb

< There is a problem when running a bond on top of vlans

also please test this with above-mentioned vlan package version, and open a new bug if it fails there as well, or post here if it works with that older vlan version.