I've opened a track against Eucalpytus based on what Dustin and I found out today.
As far as I can tell, there is no problem with uec-publish-tarball. The reason it appeared to be buggy is that it would correctly register a ramdisk-less image. The boot of that image would hang in boto's attempt to crawl the metadata service (bug 526805). Then, the user would register an image with a ramdisk, and the default ramdisk would get set (see https://${cloud_controller}:8443/#conf -> Configuration - > Default Ramdisk ). When an image was subsequently booted, it would get the default ramdisk and boot fine. However, it would have booted with errors like those seen in bug 525994 if the default ramdisk was for a kernel other than the current one. -- 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
