Finding a better solution to the 'start networking' that we have here has lead me to open bug 1047712. The case that I was debugging was actually not even improved by the 'start networking'. The issue that lead us here was that the ephemeral images for maas that we were trying to refresh have had issues coming up and woudl hit this timeout.
slangasek helped me to come up with a solution that has gotten us closer. I've replaced 'start networking' with "virtual-filesystems-emitter" (see attached) in the cloud-init-nonet job. Essentially that just gets virtual-filesystems event emitted if it hasnt already been emitted, which jump starts the networking code even while mounted MOUNTPOINT=/ is being processed. ** Attachment added: "virtual-filesystems-emitter" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+attachment/3300070/+files/virtual-filesystems-emitter -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1031065 Title: cloud-init-nonet runs 'start networking' explicitly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
