Comment 0 for bug 523625

Binary package hint: cloud-init

While testing the puppet integration in EC2 images I noticed that some instances (7 out of 10 would fail) would failed to install the puppet package. According to the console log when cloud-config-puppet runs apt-get update it gets the files from archive.ubuntu.com.

After logging into the system it turns out that the ec2 mirror have been set correctly:

ubuntu@domU-12-31-39-05-19-A6:~$ cat /etc/apt/sources.list
deb http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid main universe
deb-src http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid main universe
deb http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid-updates main universe
deb-src http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid-updates main universe
deb http://security.ubuntu.com/ubuntu lucid-security main universe
deb-src http://security.ubuntu.com/ubuntu lucid-security main universe
ubuntu@domU-12-31-39-05-19-A6:~$ sudo apt-get install puppet
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package puppet

So it seems that there is a race condition between the moment apt-get update and apt-get install puppet even though the cloud-config-puppet upstart job is set to start on started /etc/init/cloud-apt-update-upgrade.conf.