Just putting this here for late convenience. The kvm command that
libvirt runs is:
/usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 192 -smp 1 -name 20100406-no-
ramdisk -uuid 3cffa9b9-19e4-291e-21c4-9a7c17607793 -nographic -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/20100406-no-
Scott suggested this would be fixed with mountall 2.10 . I tested the
recreate with script attached here . Unfortunately, i'm not able to
reproduce the failure . I've been unable to recreate with any of
20100406, 20100402 and 20100401 .
0402 and 0401 have the old mountall
from 20100401:
$
Good news. I see the failure when recreating with beta-1 (20100317).
I'm going to mark this fix-released based on 20100406 not exhibiting the
failure and beta-1 showing it.
** Changed in: Ubuntu Lucid
Status: Confirmed = Fix Released
--
cloud-init job sometimes not running in cloud
I'm attaching a diff of the broken (beta1/20100317) and apparently fixed
manifests (20100401)
** Patch added: diff of manifests beta-1 (20100317 - 20100401)
http://launchpadlibrarian.net/43297981/beta1-to-20100401.diff
--
cloud-init job sometimes not running in cloud images without ramdisk
I'm attaching a script that recreates this.
It should run on any node controller without any hassle. it does need
partition2disk from eucalyptus, and general libvirt functionality to work.
** Attachment added: recreate script
http://launchpadlibrarian.net/42888191/recreate-531494.sh
--
** Changed in: upstart (Ubuntu Lucid)
Importance: Critical = High
** Changed in: upstart (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-2 = None
--
cloud-init job sometimes not running in cloud images without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification
I can't see any reason that this should be assigned to Upstart; if
t'other Scott is right, the system at least starts some services, in
which case Upstart must be working just fine
** Package changed: upstart (Ubuntu Lucid) = Ubuntu Lucid
--
cloud-init job sometimes not running in cloud images
Moving this out of 'incomplete'. Yesterday I gave Scott access to a
system that readily reproduces the problem.
** Changed in: upstart (Ubuntu Lucid)
Status: Incomplete = Confirmed
--
cloud-init job sometimes not running in cloud images without ramdisk
This is readily reproducible using an image launched from libvirt (ie,
no eucalyptus involved). I've sent connection information to Scott for
a system that reproduces the problem.
--
cloud-init job sometimes not running in cloud images without ramdisk
https://bugs.launchpad.net/bugs/531494
You
Updating title to reflect that it's not eucalyptus-specific, and the
racy nature of it.
** Summary changed:
- cloud-init job not running in eucalyptus without ramdisk
+ cloud-init job sometimes not running in cloud images without ramdisk
--
cloud-init job sometimes not running in cloud images
On Fri, 2010-03-19 at 04:45 +, Steve Langasek wrote:
Scott, assuming you're the correct assignee for this targeted/milestoned
bug.
** Changed in: upstart (Ubuntu Lucid)
Assignee: (unassigned) = Scott James Remnant (scott)
No; I don't know anything about this bug -- I've asked the
I just IRCd with Scott. I will try monday to get him access to a system
with console access so he can poke around.
--
cloud-init job sometimes not running in cloud images without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
12 matches
Mail list logo
