20100218 fails to boot on UEC: 'time' is not defined

Bug #523832 reported by Thierry Carrez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
High
Scott Moser
Lucid
Fix Released
High
Scott Moser

Bug Description

Binary package hint: cloud-init

UEC 20100218 daily image starts up, but fails to complete boot.
The following errors show up in the console output:

[ 3.583485] kjournald starting. Commit interval 5 seconds
[ 3.585179] EXT3-fs: mounted filesystem with ordered data mode.
[ 3.587869] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
[ 3.591663] devtmpfs: mounted
[ 3.593446] Freeing unused kernel memory: 804k freed
[ 3.597049] Write protecting the kernel read-only data: 8016k
init: plymouth main process (65) terminated with status 71
mountall: Could not connect to Plymouth
init: plymouth-splash pre-start process (290) terminated with status 111
init: plymouth-log main process (342) terminated with status 111
Caught exception reading instance dataglobal name 'time' is not defined
Could not find data source
Failed to get instance data

Related branches

Thierry Carrez (ttx)
Changed in cloud-init (Ubuntu):
assignee: nobody → Scott Moser (smoser)
importance: Undecided → High
milestone: none → lucid-alpha-3
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :

The exception message came from
cloudinit/boto_utils.py:retry_url

It was raised because the metadata service wasn't there when the boot process tried to access it.
That problem might be timing related, based on how quick Eucalyptus brings up the metadata service. We haven't seen such an issue with Eucalyptus before, but they do exist on EC2.

The fix is easy, just import time in boto_utils.py that I copied from boto.

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 Lucid):
status: Confirmed → 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.