I've verified this is still an issue with the following user-data on upstart at '1.8-0ubuntu1'.
This is re-creatable via the most recent daily image (ubuntu-raring-daily-amd64-server-20130403). I used ami-88a4c1e1.
But you can download and recreate as above. The user-data provided to recreate is below. The 'createmark' is necessary because we've disabled the 'initctl reload' call to lessen the issue. touching that file turns the call back on.
#cloud-config-archive
- filename: createmark
content: |
#cloud-boothook
#!/bin/sh
touch /run/cloud-init-upstart-reload
- content: |
#!/bin/sh
echo "==== $(date -R): user-script run ===" | tee /run/user-script.log
- filename: myjob.conf
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
- content: |
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
I've verified this is still an issue with the following user-data on upstart at '1.8-0ubuntu1'. raring- daily-amd64- server- 20130403) . I used ami-88a4c1e1.
This is re-creatable via the most recent daily image (ubuntu-
But you can download and recreate as above. The user-data provided to recreate is below. The 'createmark' is necessary because we've disabled the 'initctl reload' call to lessen the issue. touching that file turns the call back on.
#cloud- config- archive init-upstart- reload script. log job.log
- filename: createmark
content: |
#cloud-boothook
#!/bin/sh
touch /run/cloud-
- content: |
#!/bin/sh
echo "==== $(date -R): user-script run ===" | tee /run/user-
- filename: myjob.conf
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-
end script
- content: |
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True