"The underlying problem is not the error reporting itself. There is (as I pointed out earlier) a formatting problem that causes the client tools to not display the error message in many cases."
I agree that there is a formatting issue. However, failed requests should not send back a HTTP 200. It should be a 400 error code.
"I've a slightly different result on failed euca-register:
$ euca-register uecramdisk/nonexistentmanifest
'ResultSet' object has no attribute 'imageId'"
This has to do with a bug in boto. I have reported boto upstream of this issue and it has been patched in their svn head,
"The underlying problem is not the error reporting itself. There is (as I pointed out earlier) a formatting problem that causes the client tools to not display the error message in many cases."
I agree that there is a formatting issue. However, failed requests should not send back a HTTP 200. It should be a 400 error code.
"I've a slightly different result on failed euca-register:
$ euca-register uecramdisk/ nonexistentmani fest
'ResultSet' object has no attribute 'imageId'"
This has to do with a bug in boto. I have reported boto upstream of this issue and it has been patched in their svn head,
http:// code.google. com/p/boto/ issues/ detail? id=277