yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1080841@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.1-0ubuntu5

---------------
cloud-init (0.7.1-0ubuntu5) raring; urgency=low

  * catchup-751-760.patch (sync to 760)
    * DataSourceConfigDrive: allow config-drive data to come from a
      CD-ROM (LP: #1100545)
    * Allow 'sr0' to be used as a source for mount config [Vlastimil Holer]
    * do not log passwords provided via config (LP: #1096417)
    * DataSourceCloudStack: Attempt to find the 'virtual router' as provided
      from dhcp responses, rather than assuming it is the default route
      (LP: #1089989) [Gerard Dethier]
      in the CloudStack environment use virtual router rather than default route
    * notify upstart after writing upstart jobs to support filesystems that
      do not support inotify such as overlayfs (LP: #1080841)
    * fix cloud-config 'lock_password' user setup (LP: #1096423)
  * debian/README.source: minor improvements.
 -- Scott Moser <smoser@xxxxxxxxxx>   Fri, 18 Jan 2013 10:12:34 -0500

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1080841

Title:
  should reload configuration if an upstart job is added

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

Bug description:
  the overlayfs filesystem does not have inotify support.
  As a result, upstart jobs added via config (#upstart-job), will not be noticed if /etc/init is on a overlayfs filesystem.

  cloud-init should probably reload upstart configuration if it adds a job.  This is done by:
    initctl reload-configuration

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