using name in register causes internal server error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
euca2ools |
New
|
Undecided
|
Mitch Garnaat | ||
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
I'm running oneiric versions of euca2ools, boto, and cloud-utils:
$ dpkg-query --show euca2ools python-boto cloud-utils
cloud-utils 0.23-0ubuntu1
euca2ools 1.3.1-0ubuntu12
python-boto 2.0-0ubuntu1
And interacting with a 10.04 era Eucalyptus, I try to publish an image:
$ cloud-publish-image -vv --type image i386 my.img smoser-test
Wed Aug 3 11:09:56 EDT 2011: using smoser-test/my.img for --name
[image ] my.img => smoser-test/my.img
Wed Aug 3 11:09:56 EDT 2011: checking for existing registered image at smoser-
Wed Aug 3 11:09:57 EDT 2011: bundling image my.img
Wed Aug 3 11:09:57 EDT 2011: upload smoser-
Wed Aug 3 11:09:58 EDT 2011: register smoser-
failed: euca-register --name smoser-test/my.img smoser-
Warning: failed to parse error message from AWS: <unknown>:1:0: syntax error
BotoServerError: 500 Internal Server Error
Failure: 500 Internal Server Error
failed to register my.img.manifest.xml
The final command there, 'euca-register' causes a long pause, and then returns with the server internal error as show above.
Removing the '--name' will fix the issue. I'm not really sure how this should/could be handled. euca2ools or boto or cloud-utils would somehow need to know that they should not use '--name' with this server.
I've verified that the above command works fine when pointed at the Eucalyptus Community Cloud [1] as of today. I'm not sure what version that is, but I suspect its 2.0 or newer (lucid is 1.6.2).
Related branches
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Fix Released |
Changed in eucalyptus (Ubuntu Lucid): | |
importance: | Undecided → Wishlist |
Changed in euca2ools: | |
assignee: | nobody → Mitch Garnaat (mitch-garnaat) |
lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".