EC2 Volume Integration tests failing

[srijs]

The two EC2 integration tests for volumes are failing for me against the AWS account I set up.

It looks like validation of the volume ids is the problem, and AWS expects volume ids to start with vol- instead of v-.

@matthewkmayer can you confirm whether that's the same for you?

[matthewkmayer]

On my account, only the dry_run test fails.

I wonder if AWS is now doing more validating on dry run requests.

After updating the volume ids to start with vol- instead of v- we get different errors, though:

thread 'query_serialization_name' panicked at 'called `Result::unwrap()` on an `Err` value: Unknown("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Response><Errors><Error><Code>InvalidVolume.NotFound</Code><Message>The volume \'vol-00000001\' does not exist.</Message></Error></Errors><RequestID>40622108-4ab8-4221-83e4-f32304c88a3e</RequestID></Response>")'

and

hread 'dry_run' panicked at 'called `Result::unwrap()` on an `Err` value: Unknown("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Response><Errors><Error><Code>InvalidVolume.NotFound</Code><Message>The volume \'vol-00000001\' does not exist.</Message></Error></Errors><RequestID>9ed7175c-a691-47d9-bdee-202c1344fdf1</RequestID></Response>")'

More work to do on those tests. 😄