[Bug 613309] [NEW] upstart scripts do not wait for 'cloud-config' status

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Martin Pitt (pitti):

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
cloud-config-misc.conf
cloud-config-mounts.conf
cloud-config-ssh.conf
cloud-disable-ec2-metadata.conf
cloud-ec2-ebs-mounts.conf
cloud-raid.conf
cloud-runurl.conf

~~
most of these need to just add 'and cloud-config' but one or two need to just 'start on cloud-config'

~~~
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.

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: ec2 uec upstart userdata
-- 
upstart scripts do not wait for 'cloud-config' status
https://bugs.edge.launchpad.net/bugs/613309
You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber.