EC2 API doesn't return Cinder volume 'type'

Bug #1259438 reported by Rushi Agrawal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Unassigned
ec2-api
Low
Unassigned

Bug Description

When one create a volume with volume type 'standard', the EC2 API doesn't reflect this. The API response still shows volume.type as None.

Rushi Agrawal (rushiagr)
Changed in nova:
assignee: nobody → Rushi Agrawal (rushiagr)
tags: added: ec2 low-hanging-fruit volumes
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Triaged → In Progress
Rushi Agrawal (rushiagr)
tags: removed: low-hanging-fruit volumes
tags: added: volumes
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Joe Gordon (<email address hidden>) on branch: master
Review: https://review.openstack.org/61041
Reason: unfortunately this spec didn't make the cut for Juno, so marking this spec as abandoned. And it should be brought back when the spec is approved.

Sean Dague (sdague)
Changed in nova:
status: In Progress → Confirmed
assignee: Rushi Agrawal (rushiagr) → nobody
Changed in ec2-api:
status: New → Confirmed
importance: Undecided → Low
Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers