Public bug reported:
When one of the workers throws an exception in a method that is being
executed by rpc.call(), the exception is converted into a string and
passed back as 'result'. This makes it difficult to figure out if the
method call succeeded or not.
A better solution would be to:
a) log the exception in the errback before returning it.
and
b) return it separately from the result of the method.
It would be great if the receive code could actually unpack the message, and
reraise an exception if one was hit, or else unpack the result and return it so
client code doesn't have to do manual checking on the dictionary and look for
'result'
** Affects: nova
Importance: Undecided
Status: New
--
rpc.call doesn't handle errors sufficiently
https://bugs.launchpad.net/bugs/615637
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.
_______________________________________________
Mailing list: https://launchpad.net/~registry
Post to : [email protected]
Unsubscribe : https://launchpad.net/~registry
More help : https://help.launchpad.net/ListHelp
