Activity log for bug #1213925

Date Who What changed Old value New value Message
2013-08-19 13:29:41 Dimitri John Ledkov bug added bug
2013-08-19 13:29:50 Dimitri John Ledkov upstart (Ubuntu): assignee Dmitrijs Ledkovs (xnox)
2013-08-19 13:29:52 Dimitri John Ledkov upstart (Ubuntu): status New Confirmed
2013-08-19 13:29:54 Dimitri John Ledkov upstart (Ubuntu): importance Undecided Medium
2013-08-19 13:32:02 Scott Moser description When one boots ubuntu with "/" using overlayfs, the overlay would typically be empty and not have RW "/etc/" overlay directory yet. Upon writing to RO-base "/etc/", a RW "/etc" overlay directory will be created. Since a RW "/etc" didn't exist before, the inotify watches are still watching the RO-base "/etc/" directory and thus not notifying upstart to reload configurations of job files as appropriate. If the filesystem used as an overlay support inotify, than inotify events would be emitted on the RW "/etc" and thus upstart would monitor it after initctl reload-configuration. If RW "/" overlay is created before upstart is run, than when RW "/etc/" overlay is created, the RW "/" does receive inotify event that "/etc" is created. I am thus proposing to add a by-default a job that monitors all "/" events via file-bridge, and if it notices that "/etc" has been created, executes initctl reload-configuration. Thus for a lot of common cases of "/" overlayfs (live session off ubuntu desktop, lxc-cloned images with overlayfs, cloud-image overlayfs) upstart in ubuntu will be reloaded when needed. When one boots ubuntu with "/" using overlayfs, the overlay would typically be empty and not have RW "/etc/" overlay directory yet. Upon writing to RO-base "/etc/", a RW "/etc" overlay directory will be created. Since a RW "/etc" didn't exist before, the inotify watches are still watching the RO-base "/etc/" directory and thus not notifying upstart to reload configurations of job files as appropriate. If the filesystem used as an overlay support inotify, than inotify events would be emitted on the RW "/etc" and thus upstart would monitor it after initctl reload-configuration. If RW "/" overlay is created before upstart is run, than when RW "/etc/" overlay is created, the RW "/" does receive inotify event that "/etc" is created. I am thus proposing to add a by-default a job that monitors all "/" events via file-bridge, and if it notices that "/etc" has been created, executes initctl reload-configuration. Thus for a lot of common cases of "/" overlayfs (live session off ubuntu desktop, lxc-cloned images with overlayfs, cloud-image overlayfs) upstart in ubuntu will be reloaded when needed. Related bugs: * bug 882147: overlayfs does not implement inotify interfaces correctly
2013-08-19 15:29:41 Launchpad Janitor branch linked lp:~smoser/cloud-initramfs-tools/overlayroot-upstart-1213925
2013-08-29 22:47:21 Brian Murray bug added subscriber Brian Murray
2015-06-18 01:57:50 Paul Collins bug added subscriber The Canonical Sysadmins
2016-02-03 14:09:29 Dimitri John Ledkov upstart (Ubuntu): assignee Dimitri John Ledkov (xnox)