Ok. So I was looking into this more, suspecting that uec-publish-tarball was in fact, buggy.
However, it looks like the bug is in Eucalyptus is buggy in its use of images that are registered without a ramdisk. If you register image A with a ramdisk, and then register image B without a ramdisk, and start instance B, then it will be booted with the ramdisk registered with image A. ** Attachment added: "describe-images and describe-instances output" http://launchpadlibrarian.net/39667198/show-bug-525989.txt -- uec-publish-tarball yields unrunnable emi https://bugs.launchpad.net/bugs/525989 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
