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

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.2~bzr795-0ubuntu1

---------------
cloud-init (0.7.2~bzr795-0ubuntu1) raring; urgency=low

  * New upstream snapshot.
    * documentation on write-files module (LP: #1111205)
    * support for specifying package versions in package installs
    * DataSourceNoCloud: allow specifyin user-data and meta-data in
      the datasource config (LP: #1115833)
    * work around bug in upstart for now (1124384)
    * support resizing btrfs fileystems
    * parse ssh keys more correctly (LP: #1136343)
    * upstart/cloud-init-nonet.conf: handle sigterm gracefully (LP: #1015223)
    * support growing partitions (LP: #1136936)
    * use --force-unsafe-io for dpkg installations to improve speed
      This is sane as it happens on instance initialization.
    * more powerful and user-suppliable cloud-config merge mechanisms
      (LP: #1023179)
 -- Scott Moser <smoser at ubuntu.com>   Thu, 07 Mar 2013 17:33:59 -0500

** Changed in: cloud-init (Ubuntu)
       Status: Triaged => Fix Released

-- 
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:
  Fix Released
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