[Bug 1015223] Re: cloud-init-nonet main process killed by TERM signal

[Scott Moser]

Sean,
  Thanks for the suggestion of handling SIGTERM.  I wasn't sure it would work, but in testing it does seem to.
  I've verified that it works by booting a system, and looking in /var/log/dmesg.  You'll see something like:
$ grep "init:.*cloud-init.*kill" /var/log/dmesg
[   13.207358] init: cloud-init-nonet main process (679) killed by TERM signal

  After this commit, you wont see that any more.  I was confused as to whether or not it would fix it as it was unclear if the message was stating that upstart was *sending* a kill to the given process, or that that process had been killed by TERM.
  It appears to be the latter.

  Also, now we'll see something this on console output:
   cloud-init start-local running: Mon, 04 Mar 2013 19:32:27 +0000. up 3.02 seconds
   no instance data found in start-local
   cloud-init-nonet[3.95]: waiting 10 seconds for network device
   cloud-init-nonet[13.95]: waiting 120 seconds for network device
   cloud-init-nonet[22.00]: static networking is now up

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1015223

Title:
  cloud-init-nonet main process killed by TERM signal

Status in Init scripts for use on cloud images:
  Fix Committed
Status in “cloud-init” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  it has been reported in maas (and i think i've seen it other places) that the console may include:
    init: cloud-init-nonet main process (307) killed by TERM signal

  This message is scary to users, even though it is not fatal or even an
  indication of a problem.

  It occurs because the cloud-init-nonet's purpose in life is to block
  the running of cloud-init until the network devices are up.  when
  upstart recognizes that 'static-network-up' it kills cloud-init-nonet,
  which allows cloud-init to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cloud-init 0.6.3-0ubuntu1
  ProcVersionSignature: User Name 3.2.0-25.40-virtual 3.2.18
  Uname: Linux 3.2.0-25-virtual x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jun 19 17:41:24 2012
  Ec2AMI: ami-b2288bdb
  Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-precise-daily-amd64-server-20120616.manifest.xml
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-825ea7eb
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-bce
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

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