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
I must not have been clear. The lucid cloud-init package should not
run the cloud-cfg jobs until after cloud-init is finished. You should
not need the maverick sources.
--
upstart scripts do not wait for 'cloud-config' status
https://bugs.launchpad.net/bugs/613309
You received this bug
Pete,
What problem were you seeing exactly?
The upstart jobs cloud-* do not explicitly list 'cloud-config' as a 'start
on' requirement. That is by design. cloud-init starts on:
(mounted MOUNTPOINT=/ and net-device-up IFACE=eth0)
That set of events actually blocks any other upstart
Sorry about that Scott yes I had an old source for the cloud-init
upstart script your correct about the mount point.
The issue I was seeing is that the system was trying to query user data
prior to the system loading it from the meta data service. So by
waiting for cloud-init to load the
I subscribed the server team. Once this is reviewed and fixed in
maverick, we can discuss an SRU. Please subscribe ubuntu-sru then. Thank
you!
--
upstart scripts do not wait for 'cloud-config' status
https://bugs.launchpad.net/bugs/613309
You received this bug notification because you are a
** Tags added: patch
--
upstart scripts do not wait for 'cloud-config' status
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.
--
Ubuntu-server-bugs mailing list
