intermittent failed boot for lucid ec2 image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-ec2 (Ubuntu) |
Fix Released
|
High
|
Scott Moser | ||
Lucid |
Fix Released
|
High
|
Scott Moser |
Bug Description
I launched the 20091209 ec2 build in us-west-1 on i386 and the system did not come up. The system is not reachable via ssh internal or externally, and ping fails from other us-west-1 system on its internal IP.
console-output is attached, but not seemingly helpful. This bug was reported from another instance of the same AMI.
ProblemType: Bug
Architecture: i386
Date: Wed Dec 9 16:44:52 2009
DistroRelease: Ubuntu 10.04
Ec2AMI: ami-033f6e46
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-633c6d26
Package: linux-image-
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux-ec2
Tags: lucid ec2-images
Uname: Linux 2.6.32-300-ec2 i686
tags: | added: iso-testing |
Changed in linux-ec2 (Ubuntu Lucid): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in linux-ec2 (Ubuntu Lucid): | |
assignee: | nobody → smoser (scott-moser) |
assignee: | smoser (scott-moser) → nobody |
assignee: | nobody → Scott Moser (smoser) |
Just for comparison, here is console output of good boot.
Note, the ureadahead message seems to just be a red herring as it appears in both.