OpenStack Compute (nova)

volume ids are messed up in ec2_api

Bug #700893 reported by Vish Ishaya on 2011-01-10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	High	Unassigned	OpenStack Compute (nova) 2011.1 "bexar"
	Bexar	Invalid	High	Unassigned	OpenStack Compute (nova) bexar-gamma

Bug Description

Volume ids through the ec2 api are showing up as # instead of vol-#. This makes many of the ec2 commands related to volumes fail.

Vish Ishaya (vishvananda) on 2011-01-10

Changed in nova:
status:	New → In Progress
importance:	Undecided → High
assignee:	nobody → termie (termie)

Revision history for this message

termie (termie) wrote on 2011-01-25:

I think this has been resolved, will verify

Revision history for this message

Thierry Carrez (ttx) wrote on 2011-01-26:

Looks fixed to me, shows up as vol-#, creates, describes and deletes alright. Marking as FixCommitted, please reopen if you can point to a more specific failure.

Thierry Carrez (ttx) on 2011-02-07

Changed in nova:
milestone:	bexar-gamma → 2011.1
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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