no return code from cinder api calls

Bug #1968783 reported by Walt Boring
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-openstacksdk (Ubuntu)
New
Undecided
Unassigned

Bug Description

Trying to use the openstacksdk to call cinder's migrate_volume and i was not getting any return code. The cinder API returns a 400 because the volume I'm trying to migrate has a snapshot, so it will always fail.

The problem is the openstacksdk doesn't return anything from ANY of the cinder calls. Checking the volume status after the migrate_volume call is useless, because no action was taken on the volume.

So looking at the openstacksdk code, you can see almost all the cinder calls don't return anything:
No return:
https://github.com/openstack/openstacksdk/blob/master/openstack/block_storage/v3/_proxy.py#L616

No Return:
https://github.com/openstack/openstacksdk/blob/master/openstack/block_storage/v3/_proxy.py#L588

No Return:
https://github.com/openstack/openstacksdk/blob/master/openstack/block_storage/v3/_proxy.py#L495

Yet, the underlying volume object's _action() method does return the result, but the volume object doesn't return the result of that _action call here:
https://github.com/openstack/openstacksdk/blob/master/openstack/block_storage/v3/volume.py#L205

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.