[Bug 1124384] Re: reload-configuration can confuse upstart
Scott Moser
smoser at ubuntu.com
Thu Feb 14 15:33:28 UTC 2013
just a bit more info, the cloud-config content above results in writing /etc/init/part-002.conf a an upstart job.
The debug logs shown here had that file in place (from a previous boot), and cloud-init overwriting it, then calling (or not calling) reload-configuration.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
reload-configuration can confuse upstart
Status in “cloud-init” package in Ubuntu:
Confirmed
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
Under bug 1080841 we made cloud-init invoke 'initctl reload-
configuration' after it wrote a upstart job. This was necessary
because inotify is not supported on all filesystems (overlayfs being
the one of most current interst).
This seems to be causing upstart some pain, and resulting in cloud-
final (and 'rc') not being run.
Easy user-data to reproduce the problem is:
#cloud-config-archive
- content: |
#!/bin/sh
echo "==== $(date -R): user-script run ===" | tee /run/user-script.log
- content: |
#upstart-job
description "a test upstart job"
start on stopped rc RUNLEVEL=[2345]
console output
task
script
echo "==== $(date -R): upstart job run ===" | tee /run/upstart-job.log
end script
You should (and do on quantal) end up with 2 files written to /run.
I've verified that the same behavior is true on quantal. If you
change cloud-init to notify upstart about a job immediately after it
writes it, then quantal's upstart gets confused also.
Related bugs:
* bug 1080841: should reload configuration if an upstart job is added
* bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions
More information about the foundations-bugs
mailing list