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

[Scott Moser]

** Description changed:

  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
+   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 live is to block the
+ 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
+  TERM=screen-bce
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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/1015223

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

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