[Bug 1031065] Re: /sbin/resolvconf -a depends on /run/resolvconf/interface but it may not exist

[Stéphane Graber]

Problem was tracked down to cloud-init calling "start networking"
directly from one of its upstart jobs, which bypasses the start
condition of the networking job and triggers the bug.

21:16 < stgraber> [    4.598897] networking
21:16 < stgraber> [    5.016864] init: cloud-init-nonet main process (241) killed by TERM signal
21:16 < stgraber> [    5.632677] resolvconf
21:16 < stgraber> [    5.955406] virtual
21:16 < stgraber> [    5.989643] local
21:17 < stgraber> ubuntu at ip-10-202-249-151:~$ grep -r 'start networking' /etc/init/
21:17 < stgraber> /etc/init/cloud-init-nonet.conf:   start networking >/dev/null
21:17 < stgraber> smoser: ^
21:18 < stgraber> "start on mounted MOUNTPOINT=/ and stopped cloud-init-local" with clout-init-local being "start on mounted MOUNTPOINT=/"
21:18 < stgraber> so basically as soon as / is mounted, "start networking" is directly triggered by cloud-init-nonet bypassing the start condition


http://paste.ubuntu.com/1120257/ shows the process tree at the time.

** Package changed: resolvconf (Ubuntu) => cloud-init (Ubuntu)

-- 
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:
  /sbin/resolvconf -a depends on /run/resolvconf/interface but it may
  not exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+subscriptions