The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet.
~~
most of these need to just add 'and cloud-init' but one or two need to just 'start on cloud-init'
~~~
cloud-run-user-script.conf
needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)'
We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature.
Binary package hint: cloud-init
All lucid/maverick source packages,
The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet.
cloud-apt- update- upgrade. conf misc.conf mounts. conf ssh.conf ec2-metadata. conf ebs-mounts. conf
cloud-config-
cloud-config-
cloud-config-
cloud-disable-
cloud-ec2-
cloud-raid.conf
cloud-runurl.conf
~~
most of these need to just add 'and cloud-init' but one or two need to just 'start on cloud-init'
~~~ user-script. conf
cloud-run-
needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)'
We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature.