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

[Pete Crossley]

Ok Scott, yup I was seeing two issues but after I fixed my metadata
issue in UEC you are correct.  The main problem I am having is that the
user scripts run while apt-get is installing packages that are used in
my user run script.

So I will update the bug to reflect the following:

** Please have the upstart/cloud-run-user-script.conf what for a status
after the other cloud-init processes have completed.  This will allow
users to configure/execute programs that were installed during the
cloud-init process.


Thanks for taking your time to understand my issue, also allowing me to work through my miss-configuration.

** Summary changed:

- upstart scripts do not wait for 'cloud-config' status
+ cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes

** Patch removed: "This is the upstart scripts that I had to use to make this functional."
   http://launchpadlibrarian.net/53029398/cloud-init.patch

-- 
cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
https://bugs.launchpad.net/bugs/613309
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.