** Changed in: cloud-init
Status: Fix Committed = Fix Released
** Changed in: cloud-init
Milestone: 0.7.2 = None
--
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/1080841
** Description changed:
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
** Branch linked: lp:ubuntu/cloud-init
--
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/1080841
Title:
should reload configuration if an upstart job is added
To manage
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
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
fixed in trunk at revno 751.
** Changed in: cloud-init
Status: Triaged = Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
