4.0.1 client volume-transfer create is not backwards compatible with pre-rocky

[Sean McGinnis]

The client defaults all v3 calls to the volume-transfers endpoint, however previous releases of Cinder that did not include the 3.55 microversion do not have volume-transfers and should be using os-volume-transfer instead.

This only impacts the create call. Other volume transfer operations us the original endpoint.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/588673

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/588673
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=b3f3cafd1eb15cba181edff1067dc91ce56bf451
Submitter: Zuul
Branch: master

commit b3f3cafd1eb15cba181edff1067dc91ce56bf451
Author: Sean McGinnis <email address hidden>
Date: Fri Aug 3 17:04:10 2018 -0500

    Fix backwards compat for volume transfer < 3.55

    All volume transfer v3 calls were being sent to the endpoint introduced
    with microversion 3.55. This fixes backwards compatibility by routing
    calls less than 3.55 to the original API extension endpoint.

    Change-Id: I7205033ddd5be126b8614372a9fc82a2bc555f48
    Closes-bug: #1785330
    Signed-off-by: Sean McGinnis <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-cinderclient 4.1.0 release.