Cinderclient should be more informative when trying to create volume of different type out of a snapshot

[Rushi Agrawal]

When one tries to create a volume of type type2, out of a snapshot which is a snapshot of a volume of type type1, the CLI output is just "ERROR: Bad Request (HTTP 400) (Request-ID: req-<UUID>)". We should be more verbose about the error. In fact, we're more descriptive in the API call. The API response message says:

Invalid input recieved: Invalid volume_type provided (request type must match source snapshot, or be omitted). You should omit the argument.

The simple fix will be to just output this message while using the CLI

[John Griffith (john-griffith)]

Better fix would be to just go back to the way we used to do this and allow specifying a different type IMHO :)

[Duncan Thomas (duncan-thomas)]

By 'allow' you mean 'behave randomly depending on which backend(s) you've configured'? I don't think that would be an improvement...

[Sean McGinnis (sean-mcginnis)]

Automatically unassigning due to inactivity.

[Mitsuhiro Tanino (mitsuhiro-tanino)]

This was already fixed via:

https://review.openstack.org/#/c/166351/