Thanks for the cleanup. I'm OK to change that post 1.7.2 as that behavior was already there and was not the purpose of this PR. It would be better addressed in a new one.
Regarding the test that throws the exception and reading it again (my apologies for not having suggested this before), I think we should keep the assertions that verify the recorded request, to assert that the sent request is the expected one, regardless of the response or if it translates to an exception. Those could be added in a catch block and explicitly fail the test if the exception is not thrown. WDYT? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/89#issuecomment-39514966
