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

Launchpad Bug Tracker 1015223 at bugs.launchpad.net
Thu Mar 7 23:44:11 UTC 2013


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
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/cloud-init/+bug/1015223/+subscriptions



More information about the Ubuntu-server-bugs mailing list