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
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
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
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, an
** Also affects: cloud-utils (Ubuntu Lucid)
Importance: Medium
Assignee: Scott Moser (smoser)
Status: Confirmed
--
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 s
** Changed in: cloud-utils (Ubuntu)
Importance: High => Medium
** Changed in: cloud-utils (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
uec-publish-tarball yields unrunnable emi
https://bugs.launchpad.net/bugs/525989
You received this bug notification because you are a membe
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-utils (Ubuntu)
Status: New => Confirmed
--
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,
I can confirm this issue with cloud-utils 0.5-0ubuntu1
The image registered through uec-register-tarball boots OK but hangs on
metadata retrieval.
Looking at the eucalyptus side of things, we see that eucalyptus fails to serve
"ramdisk-id".
It seems that the way uec-register-tarball registers r
@Dustin,
is this a dupe of bug 522292
make sure you have current cloud-utils
--
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 lis
Note that the following steps worked just fine, from
https://help.ubuntu.com/community/UEC/BundlingImages:
ubu...@aussie:~$ TIMESTAMP=$(date +%Y%m%d%H%M%S)
ubu...@aussie:~$ RELEASE=lucid
ubu...@aussie:~$ ARCH=amd64# Or this might be i386
ubu...@aussie:~$ [ $ARCH = "amd64" ] && IARCH=x86_64 ||
Attaching output of
$ grep i-4A070989 /var/log/eucalyptus/*log > /tmp/i-4A070989.log
** Attachment added: "i-4A070989.log"
http://launchpadlibrarian.net/39558480/i-4A070989.log
--
uec-publish-tarball yields unrunnable emi
https://bugs.launchpad.net/bugs/525989
You received this bug notificat
10 matches
Mail list logo
