A note on the way that this was "fixed". * in '0.6.0-0ubuntu2', the installation of cloud-init only searches OVF and NoCloud DataSources. Neither of these have timeouts, and only look at local files. In order to search EC2, the user would then have to run 'dpkg-reconfigure cloud-init'. At 'low' priority there is a question 'cloud-init/datasources' that defaults to 'low' priority. The UEC images will pre-seed that value to have Ec2 in it.
* in subsequent releases, the first time the config is run, it will make an attempt contact the ec2 metadata service. If it can connect, then it will enable the Ec2 DataSource. If not, it will not. That covers the upgrade of 'cloud-init' on EC2 path. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in ubuntu. https://bugs.launchpad.net/bugs/635188 Title: installing cloud-init on a non-ec2/UEC server results in a 20 minute boot wait -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
