Ubuntu
cloud-init package

  1. Bug #1031065
  2. Comment #4

Comment 4 for bug 1031065

Revision history for this message
Stéphane Graber (stgraber) wrote : Re: /sbin/resolvconf -a depends on /run/resolvconf/interface but it may not exist

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@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.