@demobox I was wondering about that. Since the behaviour of that call is not crucial to this method, and there may be other gremlins lurking in softlayer (other instances where that command fails), logging a warning seems safer than rethrowing other *server errors*.
But I think you are right, if there is a neat way to check that we catch only exceptions due to HTTP code 500 that would be good. (Not sure whether that info is readily available here though ... @andreaturli ? ) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/199#issuecomment-28259836
