Thanks for explaining the details @ahgittin. So is this exception appearing only with a concrete guest, or can it appear quite often? I mean, even if this is an issue in their side, if users are going to see this exception quite often, my preference would be to add a custom fallback to the api method, to mitigate the issue. However, if the exception only appears for concrete guests with a particular configuration, and is unlikely to be a common pattern, then I'm fine with this fix.
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/199#issuecomment-28250329
