Create Volume Is Not Cinder API Version Agnostic, Causing Name + Description To Be Dropped If Using V1

Bug #1382881 reported by Auston McReynolds on 2014-10-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Medium
Unassigned

Bug Description

if you're running v1 of the cinder api, passing "name" and "description" does not work, it must be "display_name" and "display_description". today, if you're running v1, the volume created by trove has a name and description of "None".

Changed in trove:
importance: Undecided → Medium
assignee: nobody → Auston McReynolds (amcrn)
milestone: none → kilo-1
status: New → Triaged
description: updated
Auston McReynolds (amcrn) wrote :

unfortunately, i don't have the cycles to bring this to completion, but this should help someone who does:

https://gist.github.com/amcrn/eb57e411430638267a3d

the above isn't quite sufficient, because it also requires someone certifying that the v1 client behaves well with all of our other trove operations (resize volume, delete volume, attach volume, etc.)

Changed in trove:
assignee: Auston McReynolds (amcrn) → nobody
summary: - Create Volume Is Not Cinder API Version Agnostic
+ Create Volume Is Not Cinder API Version Agnostic, Causing Name +
+ Description To Be Dropped If Using V1
Changed in trove:
milestone: kilo-1 → kilo-2
Changed in trove:
assignee: nobody → Edmond Kotowski (ekotowski)
Changed in trove:
milestone: kilo-2 → kilo-3
Changed in trove:
milestone: kilo-3 → ongoing
Amrith Kumar (amrith) on 2016-04-05
Changed in trove:
assignee: Edmond Kotowski (ekotowski) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers