Activity log for bug #1080841

Date Who What changed Old value New value Message
2012-11-19 20:13:38 Scott Moser bug added bug
2012-12-04 15:10:32 Scott Moser cloud-init: milestone 0.7.2
2012-12-04 15:10:38 Scott Moser cloud-init: importance Undecided Medium
2012-12-04 15:10:46 Scott Moser cloud-init: status New Triaged
2012-12-17 17:27:57 Launchpad Janitor branch linked lp:cloud-init
2012-12-17 17:28:03 Scott Moser cloud-init: status Triaged Fix Committed
2012-12-17 17:28:58 Scott Moser bug task added cloud-init (Ubuntu)
2012-12-18 07:58:12 Yolanda Robla cloud-init (Ubuntu): status New Confirmed
2012-12-18 07:58:18 Yolanda Robla cloud-init (Ubuntu): importance Undecided Medium
2013-01-18 15:13:32 Launchpad Janitor branch linked lp:ubuntu/cloud-init
2013-01-18 15:45:15 Launchpad Janitor cloud-init (Ubuntu): status Confirmed Fix Released
2013-02-14 14:44:16 Scott Moser 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 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 Related bugs: * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image * bug 1124384: reload-configuration can confuse upstart
2013-11-19 22:01:13 Scott Moser cloud-init: status Fix Committed Fix Released
2013-11-19 22:01:13 Scott Moser cloud-init: milestone 0.7.2
2023-05-09 22:13:04 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2328