cloud-init job sometimes not running in cloud images without ramdisk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: upstart
Somewhere between uec image build 20100224 (beta1) and 2010228, the cloud-init job stopped running.
cloud-init job has:
start on (mounted MOUNTPOINT=/ and net-device-up IFACE=eth0)
I'll attach the complete diff between the 2 manifests (it is actually fairly large), but the likely candidates are:
-cloud-init 0.5.7-0ubuntu2
+cloud-init 0.5.7-0ubuntu4
-mountall 2.5
+mountall 2.6
-upstart 0.6.5-3
+upstart 0.6.5-4
The cloud-init changes are packaging only.
Two other things to note here:
a.) booting with a ramdisk "fixes" the problem
b.) instances boot fine on ec2 without ramdisk
The instance boots, and it seems that sshd is running (attempts to ssh to it receive connection refused).
There is no useful information on the serial console, nothing after the kernels messages.
So far, I've been unable to reproduce this (and get console output) when either
- mountall --debug is used
- debug initctl job in place ('start on startup' ... 'exec initctl log-priority info')
ProblemType: Bug
Architecture: amd64
Date: Wed Mar 3 11:29:10 2010
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-4
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: upstart
Uname: Linux 2.6.32-15-server x86_64
Changed in upstart (Ubuntu): | |
importance: | Undecided → Critical |
Changed in mountall (Ubuntu): | |
milestone: | none → ubuntu-10.04-beta-1 |
Changed in upstart (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in upstart (Ubuntu Lucid): | |
status: | Confirmed → Incomplete |
Changed in upstart (Ubuntu Lucid): | |
importance: | Critical → High |
milestone: | ubuntu-10.04-beta-2 → none |
I did reproduce failure with debug enabled, and attached a log of the same image successful and fail above.