Wrong archive mirror temporarily set during the boot process

Bug #523625 reported by Mathias Gug
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
Medium
Scott Moser

Bug Description

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 are run by cloud-init-puppet and cloud-apt-update-upgrade-conf. However the cloud-config-puppet upstart job is set to start on started cloud-apt-update-upgrade.

Related branches

Revision history for this message
Mathias Gug (mathiaz) wrote :
description: updated
Revision history for this message
Mathias Gug (mathiaz) wrote :

Note that the second boot messages in the attached console log were produced when the instance had been rebooted (and /var/lib/cloud/sem/cloud-init-puppet.X deleted to make sure cloud-init-puppet is re-run).

Revision history for this message
Scott Moser (smoser) wrote :

Mathias, The subject here is not consistent with current state, right?
Ie, the problem is not with incorrect selection of archive mirror.

Mathias Gug (mathiaz)
summary: - Wrong archive mirror set during the boot process
+ Wrong archive mirror temporarily set during the boot process
Revision history for this message
Mathias Gug (mathiaz) wrote :

After some debugging with scott, it turns out that starting the cloud-config-puppet job on stopped cloud-apt-update-upgrade-conf fixes the issue (rather than started).

Changed in cloud-init (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Scott Moser (smoser)
milestone: none → lucid-alpha-3
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.5.5-0ubuntu2

---------------
cloud-init (0.5.5-0ubuntu2) lucid; urgency=low

  * fix retry_url in boto_utils.py when metadata service not around
    (LP: #523832)
  * run cloud-config-puppet.conf later (LP: #523625)
 -- Scott Moser <email address hidden> Thu, 18 Feb 2010 13:04:02 -0500

Changed in cloud-init (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.