[Bug 613309] Re: cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes

[Scott Moser]

Pete,
  A build of the linked branch above will be available shortly in my ppa for lucid. https://launchpad.net/~smoser/+archive/ppa/+packages .
  I'd appreciate some test on that.  My initial test is that it functions correctly.
  To test:
- launch an instance with some user data and runcmd
- ssh to instance:
  sudo apt-add-repository ppa:smoser/ppa
  sudo apt-get install cloud-init
  sudo rm -Rf /var/lib/cloud
  sudo reboot
- ssh to instance
  - you should see changed ssh keys
  - verify that your user scripts run

I don't have a suggestion on a perfect way to prove that the dependencies are correct, but the fact that it runs generally indicates that it is good.  Ie, I'm fairly sure, that given the new 'start on' for cloud-run-user-script, it is not going to run *before* any of the other scripts.
| start on (stopped rc RUNLEVEL=[2345] \
|    and stopped cloud-apt-update-upgrade \
|    and stopped cloud-config-misc \
|    and stopped cloud-config-mounts \
|    and stopped cloud-config-puppet \
|    and stopped cloud-config-ssh \
|    and stopped cloud-disable-ec2-metadata )

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