We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.
** Changed in: maas Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1565711 Title: vlan configuration/unconfigured interfaces creates slow boot time Status in cloud-init: New Status in curtin: Triaged Status in ifupdown: New Status in MAAS: Won't Fix Bug description: maas: 1.9.1+bzr4543-0ubuntu1~trusty1 (from proposed PPA) Deploying juju bootstrap node on Ubuntu 14.04 with the following network configuration: eth0 static assigned IP address, default VLAN (no trunking) eth1 static assigned IP address, secondary VLAN eth1.2667 static assigned IP address, VLAN 2667 eth1.2668 static assigned IP address, VLAN 2668 eth1.2669 static assigned IP address, VLAN 2669 eth1.2670 static assigned IP address, VLAN 2670 eth2 unconfigured eth3 unconfigured MAAS generates a /e/n/i which auto stanzas for the VLAN devices and the unconfigured network interfaces; the upstart process which checks that network configuration is complete waits for /var/run/ifup.XXXX to exists for all auto interfaces; these will never appear for either the VLAN interfaces or the unconfigured network interfaces. As a result, boot time if very long as cloud-init and networking both take 2 minutes to timeout waiting for network interfaces that will never appear to be configured. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1565711/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp