Sure will do, I am working on this stuff right now so once the build is
done I will deploy.
--
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
Looks good Scott. Everything seem to start and execute in the correct
order.
* I purged all packages and installed via user-data and executed custom
user run script.
Which included the following:
- Custom apt repo
- Custom key for repo
- packages:
- curl
- pwgen
- pastebinit
Looking at 'cloud-config-misc.conf' script this only waits for the
filesystem. What prevents this from running prior to the cloud-init
upstart script? 'cloud-config-misc.conf' also is what the 'cloud-run-
user-script.conf' waits for to stop to allow the user scripts to run
after it. So I think
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
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
