Comment 2 for bug 1653812

That might be an option, but it occurred to me that the only reason I had trouble on reboot was that I'm using a net-iso nic setup on my vms, but not actually using net-iso. If net-iso were in use then all of the nics would be statically configured on initial deploy and the reboot problem goes away.

The approach I'm currently investigating is to reorder the service dependency so that dhcp-all-interfaces runs after network but before network-online. That way network will run, won't do anything with the interfaces since they aren't configured yet, but they'll get brought up by dhcp-all-interfaces before we hit network-online and boot continues to network-requiring services. The only major drawback I can see is that we'd still have a 5 minute delay on reboot in the "many nics, but not using net-iso" case, but that's not a production-ready configuration anyway so it should only be happening in dev and test where we don't tend to reboot anyway.